3. Hallucinations: Why AI Invents Things
Recognise that confident-sounding false statements are an inherent property of text prediction, not a fixable bug.
An AI model works by predicting the most plausible next piece of text. It doesn't look things up in a database, and it has no understanding of truth — it simply produces whatever continuation sounds most likely given what you wrote. This single mechanism is what lets it summarise, translate, draft emails and answer questions. But it also means that when the model lacks the information it needs, it doesn't stop and say "I don't know." Instead, it fills the gap with something that sounds right: a fake reference, an invented statistic, a feature that doesn't exist. This is called a hallucination. It isn't a software bug that engineers can patch; it is a direct consequence of how text prediction works. The model is optimised to be plausible, not accurate. That distinction matters every time you read an AI-generated answer.
Hallucinations are especially dangerous because they look exactly like correct answers. The model uses the same confident tone whether it is right or wrong — it has no internal "certainty meter." A hallucinated legal citation will be formatted perfectly. An invented company name will sit naturally in a sentence. You cannot tell the difference by style alone; you can only tell by checking the facts. This is why the rule of thumb is: the AI proposes, a human validates, and the depth of checking should match the stakes. A brainstorming list needs a light review; a contract clause or a medical dosage needs rigorous verification.
There is also a time dimension. Every model has a knowledge cutoff — a date after which it knows nothing because its training data stops there. If you ask about a recent law, a product launched last month, or yesterday's news, the model may still answer fluently, but it is guessing. Without an external source to draw from, any answer about recent events should be treated as unreliable. Always ask yourself: could the model actually know this, or is it filling in the blank?
The main defence against hallucinations is grounding: giving the model verified material to work from instead of relying on its internal memory. In OUPI, grounding can take several forms — attaching your own documents via knowledge bases, enabling live web search, or connecting tools that return real data. A grounded answer can point to where a claim comes from; an ungrounded answer cannot. Whenever accuracy matters — figures, names, dates, legal or medical statements — ground the model and then verify the output anyway. Grounding reduces hallucinations dramatically, but it does not eliminate them entirely.
When an AI answer sounds too good or too specific, ask it for its source. If it can't point to a real document or a search result, treat the claim as unverified. Low temperature settings also help: they make the model stick closer to the most probable (and usually safest) answer.
A practical safety rule: delegate the shaping work (drafts, summaries, reformulations, code scaffolds) and check everything that carries a decision or a commitment. The higher the stakes, the deeper your review. AI proposes, you decide.
Hallucinations are not a bug — they are a built-in property of text prediction. The model optimises for plausibility, not truth, and it uses the same confident tone whether it is right or wrong. Your defences: ground the model with documents, search or tools so it works from verified material; check facts that matter; and remember that the AI proposes while the human validates. The higher the stakes, the more you verify.