<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>LLM</title><link>https://blog.ast.moe/en/tags/llm/</link><description>Recent posts: Gorimuchu</description><generator>Hugo</generator><item><title>It's not about generating text. What kind of AI is Jev?</title><link>https://blog.ast.moe/en/blog/2026-10-01/</link><pubDate>Thu, 01 Oct 2026 11:33:14 +0900</pubDate><guid>https://blog.ast.moe/en/blog/2026-10-01/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;Even if you encounter the name “Jev,” it’s not immediately clear whether it’s an AI that answers questions in chat, a search model, or a scaled‑down version of an existing large language model. I myself built a MCP server that uses Jev, but knowing how to call its API and understanding its return values are separate issues.&lt;/p&gt;
&lt;p&gt;
&lt;span&gt;
&lt;a target="_blank" href="https://docs.typesafe.ai/introduction"&gt;
Jev from TypeSafe AI
&lt;/a&gt;
&lt;img class="external-link-icon" src="https://blog.ast.moe/images/outer-link.png" width="12" height="12" alt="" aria-hidden="true" loading="lazy"&gt;
&lt;/span&gt;
is a model that, given input information, returns a judgment on predefined questions. Rather than producing free‑form explanatory text, it returns values suitable for programmatic handling—such as the probability of a “yes” answer, probabilities for each candidate, tiered ratings, and so on. For example, you feed it a query text and have it evaluate whether it concerns an invoice inquiry, a shipping inquiry, or whether it needs to be routed to a specific person. Rather than reading the answer and continuing the conversation, the usage is that the code receiving the answer decides the next action to take.&lt;/p&gt;</description></item><item><title>How to Choose Between LLM, Embedding Models, Jev, and Classical NLP</title><link>https://blog.ast.moe/en/blog/2026-09-26-3/</link><pubDate>Sat, 26 Sep 2026 20:30:00 +0900</pubDate><guid>https://blog.ast.moe/en/blog/2026-09-26-3/</guid><description>&lt;p&gt;I often see people treating search, classification, comparison, and judgment as tasks that can simply be handed off to an LLM. If you ask it in natural language, you get a response, and you can keep asking follow‑up questions directly. That convenience is indeed useful, and I’m prone to entrusting everything to it. As a result, it’s easy to develop an impression that an LLM can solve any problem.&lt;/p&gt;
&lt;p&gt;On the other hand, even when using a judgment model like Jev, you can still give it tasks that aren’t suited for it. Asking it to hunt for information before the necessary data has been gathered, or to have it formulating an overall strategy before any candidates have been identified, is asking a limited‑purpose decision‑making tool to perform investigative work as well. If you only need to locate known terms, you can simply perform a string search without invoking a model at all.&lt;/p&gt;</description></item><item><title>LLM Quantization from the Perspective of FP6: Where to Allocate Limited Bits</title><link>https://blog.ast.moe/en/blog/2026-09-24/</link><pubDate>Thu, 24 Sep 2026 13:43:00 +0900</pubDate><guid>https://blog.ast.moe/en/blog/2026-09-24/</guid><description>&lt;p&gt;While researching quantization for LLMs, I found myself wondering in what situations FP8 would actually be useful. Further investigation revealed that FP6 and FP4 also exist. I became curious about how to store values in a 6‑bit format—an oddly sized width—and how much precision a floating‑point number with so few bits could actually represent.&lt;/p&gt;
&lt;p&gt;When you list the values representable by FP6, the spacing between adjacent numbers becomes clearly visible—a detail that is usually overlooked with the floating‑point formats we use daily. Even with the same 6 bits, the spacing changes depending on how the bits are allocated between the exponent and the mantissa. That raises the question: could we choose the representation to match the distribution of the weights?&lt;/p&gt;</description></item></channel></rss>