Every few weeks, another story surfaces: a lawyer cites fake court cases generated by ChatGPT, a student submits a paper with invented sources, a customer service bot confidently provides a refund policy that does not exist. The industry calls these failures "hallucinations," a term that frames the problem as aberrant, pathological—something to be cured. But this framing obscures a more uncomfortable truth. Large language models do not hallucinate despite their design. They hallucinate because of it.

To understand why, you must understand what these systems actually do. A large language model is, at its core, a prediction engine. Given a sequence of words, it calculates the probability distribution of what word should come next, then samples from that distribution. It does this billions of times, each prediction informed by patterns absorbed from vast training corpora. The result feels like understanding. It is not.

The confidence without comprehension

When you ask a language model about the boiling point of water, it produces the correct answer not because it understands thermodynamics but because that answer appeared countless times in its training data in contexts similar to your question. The model has learned that "boiling point of water" is statistically followed by "100 degrees Celsius" or "212 degrees Fahrenheit." This works remarkably well for common knowledge.

The problem emerges at the edges. Ask about an obscure court case, a niche historical figure, or a specific company policy, and the model faces a choice: admit uncertainty or continue predicting plausible-sounding tokens. The architecture has no native concept of "I don't know." It was trained to produce fluent, confident text. Hedging and uncertainty were not rewarded during training in the same way that coherent, authoritative-sounding prose was. So it invents. It confabulates. It produces text that sounds exactly like truth because, statistically, it resembles truth.

Why the fixes are harder than they look

The AI industry has thrown considerable resources at this problem. Retrieval-augmented generation attempts to ground responses in external documents. Reinforcement learning from human feedback tries to train models to be more cautious. Constitutional AI approaches attempt to instill principles about honesty. These methods help at the margins, but they are fighting the current.

The fundamental issue is that language models operate in token-space, not fact-space. They have no internal database of verified truths to consult, no mechanism to check their outputs against reality before emitting them. Adding retrieval systems helps, but the model can still misinterpret retrieved documents, hallucinate connections between them, or simply ignore them when the statistical pull of its training is strong enough. Teaching a model to say "I'm not sure" requires that it somehow recognize the boundary between what it knows and what it does not—a boundary that does not cleanly exist in a system that never "knew" anything in the human sense to begin with.

The honest trade-off

None of this means language models are useless. They are extraordinarily useful for tasks where approximate correctness suffices, where a human expert reviews the output, or where the cost of occasional errors is low. They excel at brainstorming, drafting, summarizing, and translating—tasks where fluency matters more than factual precision. The danger lies in deploying them as authoritative sources in domains where precision is non-negotiable: law, medicine, journalism, engineering.

The industry's preferred narrative is that hallucination is a temporary problem, a bug being squashed through better training and cleverer architectures. Perhaps. But it may be more honest to say that hallucination is the price of admission for systems that can generate novel, fluent text without true comprehension. You cannot have the creative flexibility without the confabulation risk. They emerge from the same mechanism.

Our take

The term "hallucination" does the industry a favor by suggesting something fixable, almost medical. A more accurate term might be "fabrication," but that sounds too intentional, or "statistical confabulation," but that is too clinical. What we are witnessing is a technology being deployed at scale before its fundamental limitations are widely understood—not by researchers, who understand them well, but by the businesses and individuals building workflows around these tools. The models are not lying. They are doing exactly what they were built to do. The question is whether we are building systems around them that account for this, or whether we are setting ourselves up for an endless series of embarrassing corrections.