Generative AI
Grounding, Citations, and Claim-Level Support
Design grounded generation with claim segmentation, source authority, citation entailment, uncertainty, and abstention.
By the end you can
- Distinguish grounded generation from merely including retrieved text
- Evaluate citation correctness at the level of individual claims
- Represent unsupported, conflicting, and partially supported answers
- Design generation and post-processing that preserves source authority and provenance
Grounding is a relationship between claims and evidence
An answer is grounded when its material claims are justified by permitted evidence under the task's source and time rules. The evidence can come from documents, databases, calculators, or other validated tools.
That definition is not this lesson's own. Rashkin and nine co-authors published it in Computational Linguistics in 2023, and they wrote it as a stipulation rather than an aspiration: “To this end, we present an evaluation framework, Attributable to Identified Sources (AIS), stipulating that NLG output pertaining to the external world is to be verified against an independent, provided source.” — Rashkin et al., “Measuring Attribution in Natural Language Generation Models”, abstract. Two words there carry the whole engineering burden. *Verified* is an act someone has to perform. *Independent* rules out the model's own account of itself.
AIS is not a slogan. It ships with a two-stage human annotation pipeline, validated on two conversational QA datasets, a summarisation dataset and a table-to-text dataset. Putting sources in the prompt does not meet that bar. The generator has to use the controlling evidence faithfully, it has to stop where the evidence stops, and something outside the generator has to check that it did.
Grounding is demonstrated through claim-evidence alignment, not through source proximity or citation decoration.
Visual
Grounded generation can be audited as a sequence of claim decisions
The system should preserve where each claim came from and how it was checked. Each stage below exists so that the AIS test — verification against an independent, provided source — can actually be run afterwards, on one specific claim. The alternative is asserting it about the answer as a whole, which is not a test.
- 1
Identify material claims
Segment factual, numerical, procedural, and policy assertions.
- 2
Link candidate evidence
Attach source spans or tool results to each claim.
- 3
Check support and authority
Test entailment, version, jurisdiction, and permission.
- 4
Resolve conflict
Prefer controlling sources or surface disagreement for review.
- 5
Generate with calibrated scope
State only what the evidence supports and mark uncertainty.
- 6
Attach citations and trace
Preserve source IDs, spans, transformations, and validation status.
Comparison
A citation can fail in several distinct ways
Each failure needs a different fix, and these are not categories invented for a course slide.
Three legal research products sold to professionals hallucinate between 17% and 33% of the time, despite 'hallucination-free' marketing: Lexis+ AI, Westlaw AI-Assisted Research and Ask Practical Law AI. Lexis+ AI was accurate on 65% of queries. Westlaw AI-Assisted Research was accurate 42% of the time. Ask Practical Law AI returned incomplete answers on more than 60% of queries. Magesh and five colleagues published those numbers in 2025, in the first preregistered evaluation of commercial RAG-based legal research tools.
The same paper gives the wrong-source and wrong-span failures a published name and a definition: “A response is misgrounded if key factual propositions are cited but misinterpret the source or reference an inapplicable source.” — Magesh et al., “Hallucination-Free? Assessing the Reliability of Leading AI Legal Research Tools”, §4.2 Groundedness. In their accounting, a response counts as hallucinated when it is either incorrect or misgrounded. That is the point of this section. A citation can point at a real, relevant, current document and still be wrong about what the document says.
Stale authority has been measured too, and it has a dataset. FreshQA is 600 questions deliberately sorted into never-changing, slow-changing, fast-changing and false-premise answers, scored with more than 50,000 human judgments. Vu and ten co-authors built it and published in 2024. The finding was not that some models handle time badly: “We observe that all LLMs struggle to answer questions that require fast-changing world knowledge as well as questions with false premises that need to be debunked.” — Vu et al., “FreshLLMs: Refreshing Large Language Models with Search Engine Augmentation”, abstract. Two of the four categories exist because an answer's correctness expires. Version-aware retrieval and effective dates in the citation are the fix for that column. The false-premise category is why an answer sometimes has to contradict its own question.
Wrong source
The cited document is irrelevant or lacks authority.
- Retriever or source-policy problem
- May share topic words
- Can be current but non-controlling
- Needs source selection correction
Wrong span
The document is relevant but the quoted passage does not support the claim.
- Chunk or citation-placement problem
- Can hide a nearby contradiction
- Needs span-level alignment
- Document-level links are insufficient
Overstated claim
The passage supports a narrower statement than the answer makes.
- Generation or synthesis problem
- Common with quantities and causal language
- Requires claim segmentation
- May need hedging or abstention
Stale authority
The source once controlled but has been superseded.
- Metadata and lifecycle problem
- Text can remain factually familiar
- Needs version-aware retrieval
- Citations should expose effective dates
Example
Support is not all-or-nothing
A response can carry several claim states at once. That is why a single verdict on a whole answer measures almost nothing.
FActScore was built on exactly that complaint. Its abstract opens on the problem this section describes: “Evaluating the factuality of long-form text generated by large language models (LMs) is non-trivial because (1) generations often contain a mixture of supported and unsupported pieces of information, making binary judgments of quality inadequate, and (2) human evaluation is time-consuming and costly.” — Min et al., “FActScore: Fine-grained Atomic Evaluation of Factual Precision in Long Form Text Generation”, abstract.
The fix is to break a generation into atomic facts and score the percentage of them supported by a reliable knowledge source. In human evaluation of people biographies generated by commercial LMs, ChatGPT achieved only 58%. The automated estimator of FActScore has an error rate of less than 2%, and it was used to evaluate 6,500 generations from a new set of 13 recent LMs — a run that would have cost $26K to evaluate by humans. The mixed states below are what a per-claim score counts. A single supported-or-not label would collapse all six into one number that names none of them.
- Directly supported: The policy states a thirty-day deadline in a controlling clause.
- Derived by tool: A calculator converts the deadline into a date from a verified start date.
- Partially supported: The source permits an exception but does not establish that the user qualifies.
- Conflicted: Two current documents disagree and the authority hierarchy is unresolved.
- Unsupported: The answer proposes a rationale or outcome absent from any permitted evidence.
- Out of scope: The question requires a jurisdiction or personal fact that the system does not have.
Key idea
A citation generator can produce plausible links without support
Models learn the visual and rhetorical form of citations. They can invent identifiers, attach a real source to the wrong claim, or cite a passage that mentions the topic without entailing the statement.
The form can be good enough to survive a federal docket. Six non-existent judicial opinions, with fake quotes and citations, produced by ChatGPT, were filed in Mata v. Avianca, Inc. and defended after the court questioned them. Judge P. Kevin Castel's sanctions opinion of 22 June 2023 opens on it: “Peter LoDuca, Steven A. Schwartz and the law firm of Levidow, Levidow & Oberman P.C. (the "Levidow Firm") (collectively, "Respondents") abandoned their responsibilities when they submitted non-existent judicial opinions with fake quotes and citations created by the artificial intelligence tool ChatGPT, then continued to stand by the fake opinions after judicial orders called their existence into question.” — Judge P. Kevin Castel, Opinion and Order on Sanctions, Mata v. Avianca, Inc., 22 June 2023. The court imposed a Rule 11 penalty of $5,000, jointly and severally, payable into the Registry of the Court within 14 days. It also ordered the respondents to write to each real judge falsely named as the author of a fabricated opinion.
Nothing about those citations announced itself as fabricated. That is the failure mode. Use source IDs supplied by the application, constrain citation choices to retrieved records, and verify claim-span alignment. High-risk answers should expose unsupported claims rather than fill every citation slot.
Citation formatting is an interface feature; citation validity is an evidence relationship.
Case
Four generative search engines, and half the sentences unsupported
Four generative search engines were audited by hand, sentence by sentence: Bing Chat, NeevaAI, perplexity.ai and YouChat. Liu and two colleagues published the result in 2023, and the abstract states it without cushioning: “on average, a mere 51.5% of generated sentences are fully supported by citations and only 74.5% of citations support their associated sentence”.
Read the two figures separately. The first is about sentences. Roughly half of what these products generated was not fully backed by the citations attached to it. The second is about the links themselves. About a quarter of them pointed at something that did not support the sentence beside them. Both are measures of support, not of truth. A sentence can be fully supported by its citation and still be wrong, if the source is.
Figure
Case
A citation benchmark left the best models short of full support
ALCE is a benchmark for automatic evaluation of LLM citations, and it found the same shape. On the ELI5 dataset, “even the best models lack complete citation support 50% of the time”. Gao and three colleagues built it and published in 2023.
A hand audit of four commercial products and an automated benchmark, run by different groups on different data, land on the same half. Form is cheap. Support is not.
Position
Citations are a claim about the work, not the work
There is a measured answer to how often a citation supports the sentence it is attached to, and it is not the answer the interface implies. The hand audit of four generative search engines reported that “on average, a mere 51.5% of generated sentences are fully supported by citations and only 74.5% of citations support their associated sentence”. The second number is the one to sit with. It is not about whole answers. It is about the links themselves, about a quarter of which pointed at something that did not support the claim beside them. A benchmark built for the question found the same shape: on ALCE's ELI5 data, even the best models lack complete citation support 50% of the time.
The honest case for retrieval is a pair of numbers from one research group, and it is narrower than the marketing. Dahl and three colleagues measured the ungrounded baseline first: “Using OpenAI's ChatGPT 4 and other public models, we show that LLMs hallucinate at least 58% of the time, struggle to predict their own hallucinations, and often uncritically accept users' incorrect legal assumptions.” — Dahl et al., “Large Legal Fictions: Profiling Legal Hallucinations in Large Language Models”, abstract. Then largely the same authors measured the retrieval-backed commercial tools and found 17% to 33%. Retrieval moved the rate a long way down. It did not move it to zero. The products carrying the improved number were sold as 'hallucination-free'.
So the count of citations in an answer is not a measure of grounding. A product that fills every slot has demonstrated only that it can fill slots. The figure worth reporting is claim-level, and it is an uncomfortable one to publish: how many material claims were fully supported, how many were partly supported, and how many the system should have declined to make. A product that reports that will look worse than one claiming to be free of the problem. It is also the one you can defend.
Grounding is counted in claims that survived a check, not in links that were rendered.
Steps
Run a claim-support audit
Use representative answers and inspect both supported and unsupported material. The unit of analysis is not something this lesson is proposing. RAGTruth is a corpus of nearly 18,000 naturally generated RAG responses, annotated by hand at both the case level and the word level, with hallucination intensity, across question answering, data-to-text writing and news summarisation. Its premise is the one that makes the steps below necessary: “Despite the integration of RAG, LLMs may still present unsupported or contradictory claims to the retrieved contents.” — Niu et al., “RAGTruth: A Hallucination Corpus for Developing Trustworthy Retrieval-Augmented Language Models”, abstract.
Two things follow for your own audit. Word-level annotation over nearly 18,000 responses is what claim-level auditing looks like at scale, so the cost is known rather than speculative. And on that data a small fine-tuned model matched GPT-4 prompt-based hallucination detection, which means a labelled corpus of your own answers is worth more than a larger judge model applied to unlabelled ones.
1. Segment the answer
Mark each material factual, numerical, procedural, and causal claim.
2. Assign evidence
Link source spans, database records, or tool outputs.
3. Check authority and time
Verify jurisdiction, version, freshness, and access.
4. Rate support strength
Direct, derived, partial, conflicting, unsupported, or out of scope.
5. Inspect language scope
Find certainty, causality, and quantification beyond the evidence.
6. Test abstention
Confirm the system narrows or stops when support is inadequate.
Grounded answers make their epistemic boundary visible
Products that ground well tell users which claims are sourced, derived, uncertain, or unavailable. That clarity is worth more than the maximum number of links. In the audit of four generative search engines, a full-looking set of links was worth 74.5% of citations supporting their associated sentence. In tools marketed as free of the problem, retrieval still left 17% to 33% behind.
The next lesson evaluates and debugs the entire RAG pipeline. Claim support becomes one outcome among retrieval, context, latency, and abstention metrics.
Key takeaways
- Grounding is the AIS relationship: output about the external world must be verified against an independent, provided source, not merely placed next to one.
- Retrieved context and citation presence do not establish support — a hand audit of four generative search engines found 51.5% of sentences fully supported and 74.5% of citations supporting their sentence.
- Wrong source, wrong span, overstatement, and stale authority are distinct failures; Magesh and colleagues name the first two 'misgrounded' and FreshQA measures the last with fast-changing and false-premise questions.
- Claims may be directly supported, tool-derived, partial, conflicting, unsupported, or out of scope, which is why FActScore scores atomic facts instead of whole answers.
- Application-supplied source IDs and span links improve traceability without guaranteeing correctness; Mata v. Avianca shows fabricated citations that looked entirely conventional.
- Retrieval reduces the failure rate without removing it — at least 58% ungrounded against 17% to 33% with retrieval — so reliable systems still narrow, qualify, or abstain.