Hallucination Types in Language Models: A Complete Guide › What Is Hallucination in Language Models?

Hallucination refers to generated content that is unfaithful to a provided source, factually incorrect, or entirely fabricated. The term covers a wide range of failure modes, from subtle factual inaccuracies to wholesale invention of events, people, or citations that do not exist.

Language models are trained to produce fluent, coherent text. During pretraining, they learn patterns from vast quantities of text and optimize for next-token prediction. This objective rewards text that looks like good writing, not text that is factually grounded. A model that generates "The Eiffel Tower was built in 1889" and "The Eiffel Tower was built in 1901" produces both with essentially equivalent fluency from the model's perspective. The training loss does not directly penalize factual errors.

This creates a fundamental tension: the skills that make language models useful (fluency, coherence, breadth of knowledge) are separate from the skills needed to be reliably correct. Fluency is easier to learn at scale than factual accuracy, and the model's confidence, reflected in the way it generates text, does not track its correctness. The model has no internal alarm that fires when it transitions from retrieving a well-attested fact to generating a plausible-sounding pattern.

The problem compounds in certain conditions. When the correct answer is rare in training data, the model has less evidence to draw on and is more likely to substitute a common-but-wrong variant. When the model needs to generalize beyond what it has seen, it falls back on pattern-matching rather than factual recall. When it is asked to synthesize information across multiple sources, small inconsistencies in the training data can lead to conflation errors where facts from different entities get combined into a single, plausible-but-wrong claim. In each of these settings, the model's tendency to produce plausible-sounding text overrides whatever factual knowledge it has acquired, and the result is a hallucination that is difficult to distinguish from correct output.

To understand the scale of the problem, consider what research has found across deployment contexts. Studies of medical question-answering systems found hallucination rates as high as 30-40% on detailed clinical questions. Legal summarization tools produced factual errors in descriptions of case outcomes in over a quarter of tested documents. Coding assistants generated plausible-looking but non-functional code that referenced APIs or methods that didn't exist. In each domain, the errors were not random noise but structured, plausible fabrications that fit the expected format of correct output.

Just as we saw with bias in prior sections, where models absorb and reproduce statistical patterns from training data in ways that can cause harm, hallucination arises from the same underlying mechanism. The model learns what text looks like without always learning what is true. Bias and hallucination are, in a sense, two faces of the same problem: statistical learning without grounded understanding. A model can learn to produce text that statistically resembles factual writing without ever having a representation of truth as distinct from plausible-sounding patterns.

Before treating hallucination as a single monolithic problem, it is worth asking: why classify it into types at all? The answer is that different hallucination types require fundamentally different detection strategies, different mitigation approaches, and different evaluation frameworks.

Intrinsic hallucinations, which contradict a source document, can be caught by comparing output to source using natural language inference. Extrinsic hallucinations, which add ungrounded content, require external knowledge to detect. Fabrications require verification against knowledge bases or retrieval systems. Inconsistencies can be caught with self-consistency checks that require no external knowledge at all. Without a taxonomy, you cannot choose the right tool for the problem you are facing.

The taxonomy also clarifies what "fixing" hallucination means in different contexts. A summarization system might be optimized specifically to eliminate intrinsic hallucinations while accepting some extrinsic ones, if the task only requires staying within the source document. A knowledge-intensive QA system might tolerate inconsistency but must minimize fabrication. A conversational assistant might prioritize reducing cross-turn inconsistency. The right definition of success depends on the task, and the taxonomy provides the vocabulary for specifying it.

This chapter focuses on the types of hallucination rather than their causes. The Hallucination Causes chapter will examine why hallucinations occur, covering training data issues, exposure bias, knowledge gaps, and generation pressure. Here, you will learn to recognize and classify hallucinations by their form and relationship to source material.