Skip to content

AI, decoded

Are AI hallucinations a data problem or a model problem?

Largely a data problem, especially in the enterprise. A language model predicts plausible text; when it lacks the right grounding it fills the gap with something that sounds right, which we call a hallucination. Much of that comes from the data layer — missing context, stale or contradictory sources, poor retrieval, no single source of truth. You can't fully train hallucination out of the model, but you can starve it: ground answers in trusted, current data and the model has less reason to invent. The model generates; the data decides whether it has the truth to generate from. Neo4j's Sudhir Hasbe told Chain of Thought that customers using only vector-search RAG see around 60% to 65% accuracy, while some combining graph and vector search are well above 90%.

· Updated · Chain of Thought

Level 1: How AI works · 1.3 Why AI makes things up

AI Evaluation & ReliabilityRAG & Retrieval

  • 2 episodes
  • 2 guest clips
  • 8 glossary terms
Two identical-looking speech bubbles, one cracked down the side, beside the words: plausible does not equal true.

In detail

Why models hallucinate at all

A language model is built to produce plausible text, not to know what’s true. Given a prompt, it predicts the most likely continuation. When the right facts aren’t in front of it, “most likely” and “correct” come apart, and it generates something fluent and wrong. Hallucination isn’t a glitch bolted onto an otherwise truthful system; it’s the default behavior of a plausibility engine without grounding. The phrase is Dan Klein’s: in episode 54 at 3:30 he says “we have built not truth engines, not reliability engines, we’ve built plausibility engines.”

The data layer is where the truth comes from

That reframes the fix. If the model invents when it lacks grounding, the grounding is where to work. Missing context, outdated or conflicting sources, weak retrieval, and the absence of a single source of truth all push the model toward making things up. Treating hallucination as a pure model defect leads to endless prompt-tweaking; treating it as a data-architecture problem points you at the cause you control. Sudhir Hasbe makes the enterprise version of this point in episode 55 at 2:03: teams have to work out the data architecture that gives an agent enterprise knowledge, so its decisions are right and auditable.

The model side of the story

Data isn’t the whole explanation, and the research says so. In Why Language Models Hallucinate, Adam Tauman Kalai and colleagues argue that models hallucinate partly because training and evaluation reward guessing over admitting uncertainty: on a benchmark scored only on accuracy, a model that guesses beats one that says “I don’t know.” On that view, part of the fix sits in how base models are trained and how public benchmarks are scored, which a team building on a provider’s model doesn’t control. What it does control is the data and retrieval layer, any fine-tuning it does itself, and whether its own evals reward an honest “I don’t know” over a confident guess. Why do LLMs hallucinate? covers the mechanism in more depth.

What reduces it

Ground answers in trusted, current data — retrieval over authoritative sources, structured knowledge the model can lean on, clear provenance. You won’t get to zero, because the model is still a probabilistic generator. Dan Klein’s point at 29:24 in episode 54 is that even a system handed the right answer can still say something different, which is why he argues the model itself should be architected for reliability too. But the more reliably you feed it the truth, the less room it has to invent one. The research backs the direction: Shuster et al. (2021) found that retrieval-augmented dialogue models substantially reduced knowledge hallucination in human evaluations.

Disclosure: Episodes 54 and 55 were sponsored by Galileo, the Season 3 presenting sponsor (episode 54 opening read, episode 55 read at 1:37).

Are AI hallucinations a data problem? The same model on broken and on solid grounding The same model, a plausibility engine that predicts the most likely continuation, runs twice. Top, without grounding: the data underneath has gaps, namely missing context, stale or contradictory sources, weak retrieval, and no single source of truth, so the model fills the gap with something that sounds right, and the answer can come out fluent and wrong. Bottom, grounded: the data underneath is trusted and current, with retrieval over authoritative sources, structured knowledge the model can lean on, and clear provenance, so the model has less room to invent. It is not zero, because the model is still a probabilistic generator. Underneath: the model generates; your data decides what it has to work with. Dan Klein, episode 54: we've built plausibility engines, not truth engines. Sudhir Hasbe, episode 55: in enterprise AI, figure out your data architecture. Same model, different ground A plausibility engine fills any gap with something that sounds right. What's underneath decides the gap. WHAT IT'S STANDING ON THE MODEL WHAT COMES OUT WITHOUT GROUNDING missing context stale or contradictory sources weak retrieval no single source of truth model predicts the most likely continuation Can be fluent and wrong “Most likely” and “correct” come apart, and the invention sounds just as sure. GROUNDED IN TRUSTED DATA trusted, current sources retrieval over authoritative data structured knowledge to lean on clear provenance same model predicts the most likely continuation Less room to invent Not zero: it's still a probabilistic generator. It just has less to fill in. The model generates; your data decides what it has to work with. “Plausibility engines,” not truth engines: Dan Klein, ep 54. Enterprise data architecture: Sudhir Hasbe, ep 55.
Hallucination is the default of a plausibility engine without grounding. “Plausibility engines” is Dan Klein’s phrase from episode 54; the enterprise data-architecture framing is Neo4j’s Sudhir Hasbe’s, episode 55. Download the image

Hear it from the guest

“Ultimately, they are assembling plausible outputs on the fly. And it's so easy for those things to be plausible, but not true. The bottom line is we have built not truth engines, not reliability engines, we've built plausibility engines.”
Watch on YouTube
“You all have to figure out what's your data architecture to provide that enterprise knowledge to the agentic system so that you can make right decisions and you can audit the decisions”
Watch on YouTube

Quotes lightly edited to remove filler words.

From the conversation

This explainer is drawn from these episodes — each carries its full transcript.

Concepts in this explainer

GroundingAI HallucinationLarge Language ModelAccuracyAI BenchmarkAI EvaluationFine-TuningRetrieval-Augmented Generation (RAG)