What does "fine-tuning is for form, not facts" mean for an LLM?
answer
- behaviour transfers, knowledge barely does
- one exposure per fact, thousands per shape
- confident, well-formatted, wrong
- retrieve the volatile, tune the shape
- continued pretraining is the knowledge lever
basics
~20 sFine-tuning reliably changes how a model behaves — its format, tone and judgement — but not what it knows. Training on facts the base model never learned mostly teaches it to assert unfamiliar claims confidently, which raises the hallucination rate.
solid answer
~50 sFine-tuning updates weights on examples of a behaviour, so what it transfers reliably is *shape*: output structure, register, labelling conventions, an implicit threshold you can demonstrate but not describe. What it does not do well is install new knowledge. When training examples are full of entities and facts the base model never saw, the model cannot learn them from a few thousand rows; what it learns is the pattern "produce a confident, specific-sounding claim in this slot". The measured effect is a hallucination rate that climbs roughly in proportion to the share of unknown facts in the training data. The tools that actually change knowledge are retrieval at query time, for anything current or volatile, and continued pretraining on a large domain corpus when the vocabulary and register themselves are alien. In practice you tune for form and retrieve for facts, in the same system.
go deeper
Remember the slogan and one concrete consequence: training on facts the model never learned produces confident wrong answers. Be able to say that current or changing information belongs in the prompt via retrieval.
Explain the mechanism — a fine-tuning set gives massive repeated signal about output shape and almost none about any individual fact — and distinguish fine-tuning from continued pretraining as the actual knowledge lever.
Show how you would audit a proposed dataset row by row, moving facts from completions into prompts, and describe why a well-formatted hallucination is harder for human reviewers to catch than an obviously generic one.
Own the systems framing: which layer is responsible for currency, what the review burden becomes once outputs look authoritative, and how you keep a knowledge boundary explicit so nobody quietly re-solves a retrieval problem with a training run.
## The slogan "Fine-tuning is for form, not facts" is the single most quoted heuristic in this decision, and interviewers use it to check that you understand *why* it holds rather than that you have heard it. ## Why form transfers and facts do not Fine-tuning shows the model a few hundred to a few tens of thousands of examples and nudges weights toward reproducing them. That is an enormous amount of signal about *how* an answer should look — its structure, its length, its hedging, which fields appear in which order, when to escalate rather than decide — because every example demonstrates the same shape. It is a trivial amount of signal about any individual fact, which appears once or twice. Base models acquired their knowledge from trillions of tokens seen many times in many phrasings; a fine-tuning set is orders of magnitude smaller and touches each fact once. So the model does learn something from fact-dense examples — just not the facts. It learns the *behaviour* of confidently producing a specific-sounding claim in that position. Applied to a new input whose true answer it does not know, it produces one anyway. This is why the observed hallucination rate rises roughly with the proportion of training rows containing knowledge the base model lacked. ## The failure in practice A compliance team fine-tunes on two thousand past adjudication memos. Each memo contains entity histories, prior case references and ownership chains the base model has never encountered. The tune succeeds at the thing it was meant to do — the memos now read exactly like house memos — and simultaneously produces fluent, well-structured, confidently wrong entity histories on new alerts. Worse, the failure is harder to catch than before, because the output now carries every surface marker of a competent internal document. Reviewers who would have flagged an obviously-generic answer wave through a house-formatted one. The fix is not a better dataset in the same shape. It is to *remove* the facts from the training target and supply them at inference: the memo structure and escalation voice come from the tune; the entity record, the prior decisions and the current sanctions list come from retrieval, because the list changes weekly and no weight update tracks that. ## What does change knowledge **Retrieval.** Put the relevant records in the context at query time. This is the right answer for anything that changes, anything that must be cited, and anything where being able to point at a source matters. **Continued pretraining.** Train on a large unlabeled corpus — hundreds of millions to billions of tokens of internal documents — with the same objective used to build the base model. This genuinely shifts what the model has absorbed, and it is the option when the *domain language itself* is alien: unusual notation, a specialist register, terminology used differently from ordinary usage. It is a different-sized commitment from fine-tuning, in compute and in data, and it is often confused with it in interviews. Continued pretraining is also usually followed by fine-tuning, because pretraining alone does not produce an instruction-following assistant. **A bigger or newer base model.** Sometimes the knowledge gap is simply a weaker model, and the cheapest fix is to move. ## How to draw the line in a real dataset Go through a sample of your training examples and ask, for each piece of information in the target output, whether it could be derived from the input plus the base model's general knowledge. If yes, it is form — the model is learning how to arrange what it was given. If no, it is a fact the example is silently asking the model to memorize, and it should have been in the input, retrieved, instead of in the target. That rewriting exercise usually converts a bad fine-tuning set into a good one: the same memos, but with the entity file and policy excerpt present in the prompt rather than assumed in the completion. ## Nuance worth stating The rule is a heuristic, not a theorem. Fine-tuning does move factual behaviour at the margins — heavily repeated, highly consistent facts can stick, and tuning can teach a model *which* of the things it already half-knows to prefer. And style is not cosmetic: a tuned refusal threshold or escalation criterion is a genuine capability change. The honest framing is that fine-tuning is a high-bandwidth channel for behaviour and a very low-bandwidth, high-risk channel for knowledge, so you should never rely on it for the latter. ## What a strong answer says Name the mechanism (small data, one exposure per fact, huge repeated signal about shape), name the concrete failure (confident well-formatted wrong answers), and name the two alternatives with the distinction between them (retrieval for volatile facts, continued pretraining for alien domains). Then say the two are combined, not chosen between.
- If fine-tuning cannot teach facts, why does continued pretraining manage it?Scale and objective. Continued pretraining runs the original next-token objective over hundreds of millions to billions of tokens, so each fact appears many times in many phrasings — the same conditions under which the base model learned anything at all. A fine-tuning set is orders of magnitude smaller and shows each fact once or twice, which is enough to shape output format and nowhere near enough to encode knowledge. Continued pretraining also usually needs a subsequent instruction-tuning stage to be usable.
- How would you rewrite a fact-dense fine-tuning dataset so it teaches form safely?Move the facts from the completion into the prompt. For each example, include the source records the writer actually consulted — the entity file, the policy excerpt, the prior decision — so the target output only ever rearranges and judges information present in the input. The model then learns "given these sources, produce this memo", which is exactly the behaviour it will be asked for at inference time alongside retrieval.
- Isn't a tuned escalation threshold a knowledge change rather than a form change?It is a capability change, which is why "form" is a slightly lossy word. The useful distinction is between information that must be current and specific — entities, prices, list membership — and dispositions that are stable and demonstrable, like where to draw a risk line. Dispositions are exactly what training conveys well, because every example reinforces the same boundary. Volatile specifics are what it conveys badly.
Coaching someone's writing voice for a month reliably changes how they write. It does not put today's newspaper in their head — and if you only ever praised confident prose, they will now invent the headlines fluently.
saying these in an interview costs you the question
- Fine-tuning is how you teach the model our internal data
- More training examples will eventually make the facts stick
- Hallucination after tuning means the learning rate was wrong
- Continued pretraining and fine-tuning are the same thing
- Once tuned, the model no longer needs retrieval