A common intuition is 'fine-tune the model on our company's facts so it knows them'. In practice this often INCREASES hallucination, not decreases. Explain the mechanism and what to do instead.
Fine-tuning teaches the confident domain voice fast, but rarely memorizes new facts. The model gains authority without knowledge, so it confabulates more. Use RAG for facts.
Imagine coaching someone to sound like a doctor. After a weekend course they nail the white-coat voice, the jargon, the calm certainty. But they did not actually learn medicine in a weekend. Now they answer every health question with total confidence, and when they do not know something, they make it up in that same convincing doctor voice. That is worse than before, because people believe them. Fine-tuning on your company facts does the same thing to a model. It picks up the confident in-house style from a few hundred examples, but cannot truly memorize the facts. So it bluffs in your brand voice. The fix is to hand it the real records to read at answer time, which is what retrieval does.
Detailed answer & concept explanation~8 min readEverything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
5 min: behavior vs facts asymmetry + why small fine-tunes cannot memorize + confidence without knowledge mechanism + the 2024 hallucination finding + retrieval as the fix + combined stack and evaluation.
| Property | Fine-tuning installs it well | RAG installs it well |
|---|---|---|
| Tone and domain voice | Yes, in hundreds of examples | No, prompt cannot reliably enforce it |
| Specific facts and numbers | No, weak lossy traces, confabulation risk | Yes, grounded in retrieved source |
| Output format and schema | Yes, behavior transfers fast | Partially, brittle via prompt only |
| Freshness of facts | Stale at training time, retrain needed | Seconds to update via reindex |
| Effect on confidence | Raises confidence regardless of knowledge | Confidence tied to retrieved evidence |
Real products, models, and research that use this idea.
- Teams fine-tuning Llama 4 on internal wikis report the model adopts house tone but invents plausible-sounding policy numbers when asked about edge cases not in the set.
- OpenAI's fine-tuning guidance steers users toward retrieval for knowledge and reserves fine-tuning for tone, format, and consistent behavior.
- Perplexity grounds answers in retrieved live sources rather than baking facts into weights, then uses lightly tuned GPT-5.5 and Claude Opus 4.7 for citation-style synthesis.
- Anthropic enterprise deployments commonly fine-tune Claude Opus 4.7 for refusal policy and brand voice while layering RAG over Confluence and Notion for current facts.
- Medical and legal copilots from 2025 to 2026 pair a domain-tuned base with mandatory retrieval, since a confident wrong drug dose or citation is a liability, not a quirk.
What an interviewer would ask next. Try answering before peeking at the approach.
QHow would you design an eval that catches confident confabulation rather than just measuring accuracy?
QIf you must put some knowledge in weights, what makes a fact safe to fine-tune versus dangerous?
Don't say thisRed flags and common mistakes that signal junior thinking. Click to expand.
Red flags and common mistakes that signal junior thinking. Click to expand.
Assuming a few thousand fine-tuning examples can install facts the way pretraining did. They install the confident voice instead, so the model bluffs more, not less.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.
Same topic, related formats. Practice these next.