|
Hallucination and confabulation
the question Ji and colleagues (2023) surveyed the term across text generation and kept a useful split: output that contradicts the source it was given (intrinsic), and output that cannot be checked against that source at all (extrinsic) [paraphrase, not a quotation]. The second kind is not always false. It is unsupported, which is a different failure. the classic findings Maynez and colleagues (2020) had people read summaries written by neural systems and mark anything not supported by the article. Unsupported content was common, and the usual automatic overlap scores for summaries tracked it poorly [paraphrase, not a quotation]. Lin, Hilton & Evans (2022) wrote TruthfulQA, questions chosen because people often answer them wrongly from popular misconceptions. In their tests the larger models were generally less truthful, because they had learned the misconception more fluently [paraphrase, not a quotation]. A partial counterweight is that models carry some signal about their own reliability. Kadavath and colleagues (2022) found that larger models, asked to estimate the chance that their own answer was right, were reasonably calibrated on many tasks [paraphrase, not a quotation]. Knowing and saying are different steps; see calibration.
the human side Nisbett & Wilson (1977) is the classic case of people explaining their own behaviour fluently and wrongly. In neurology, confabulation names something sharper, in some patients with memory loss, who answer questions about their past with sincere invention. The common thread is that fluency is produced by one process and checking by another, and the second can be missing while the first runs fine. live debates Is "hallucination" the right word? Psychiatrists objected early. Østergaard & Nielbo (2023) argue the term is clinically inaccurate, since a model has no perception to misfire, and that it risks stigmatising people who hallucinate; Emsley (2023) prefers "fabrication" and "falsification". Hicks, Humphries & Slater (2024) go further, arguing in Harry Frankfurt's sense that such output is bullshit: produced without regard to truth, rather than a failed attempt at it [paraphrase, not a quotation]. The disagreement is not only verbal. Each label implies a different mechanism and a different fix. Is it inevitable? Xu, Jain & Kankanhalli (2024) give a formal argument, from computability, that any computable language model will hallucinate on some inputs. Kalai & Vempala (2023) make a statistical one: a model that is calibrated must produce false statements about facts that appear rarely in training, at a rate tied to how many facts appear only once [paraphrase, not a quotation]. Kalai et al. (2025) add an incentive account: if benchmarks grade right-or-wrong and give no credit for abstaining, training rewards confident guessing. Critics answer that a lower bound in theory says little about the rate in practice, which retrieval and abstention can drive down. methodological critiques Measuring it. Most measures need a reference. FActScore (Min et al., 2023) splits long answers into atomic facts and checks each against a knowledge source, which makes results depend on the source and on the automatic checker. Semantic entropy (Kuhn, Gal & Farquhar, 2023) (Farquhar et al., 2024) needs no reference: it samples several answers, clusters them by meaning, and flags high disagreement. Its limit is built in: it catches confabulations, answers that vary arbitrarily, and cannot catch errors the model makes consistently. The survey by Huang et al. (2023) separates factuality errors from faithfulness errors (departures from the given input), the distinction Maynez et al. (2020) drew for summaries. A rate reported without saying which kind, against which reference, is not comparable with another. still open Whether retrieval of real sources and abstaining when unsure (the reject option) can close most of the gap; whether confidence can be shown to readers in a way they use; and whether people trust a fluent wrong answer more than a hesitant right one, which is a question for automation bias. Reading list
see also
|
![]()
rev. Oct 24 2026