Fabricated Citations
Issue: Model Cites Sources That Don’t Exist
Frequency: Occasional
Symptoms
- Citation references non-existent document
- Made-up document titles or authors
- URLs that lead nowhere
- Plausible-sounding but fake references
Root Cause When model generates content beyond retrieved context, it may also generate citations for that content, creating entirely fabricated references.
Example
Query: "What research supports this treatment?"
Agent response: "According to the Johnson et al. (2023) study
published in the Journal of Medical Research, the treatment
showed 89% efficacy [1]."
Reality:
- No such study exists
- No "Journal of Medical Research"
- Citation is completely fabricated
Result: User can't verify, may cite fake study themselves
Real Incidents
- Lawyers cited 6 fake ChatGPT-generated cases (Avianca lawsuit)
- Legal RAG tools generate plausible-looking fake citations
Mitigation Strategies
- Citation validation: Verify all references exist
- Closed-book prevention: Only cite from retrieved content
- URL verification: Check URLs are valid before including
- Source registry: Only allow citations to known sources
- Citation generation from extraction: Build citations from metadata
- Warning labels: Flag citations that couldn’t be verified
Detection
- Validate all citations against source index
- Check URLs for accessibility
- Cross-reference author/title combinations
- Flag citations not in retrieved documents
Mitigation Strategies
Prevention
Implement query-answer consistency validation: Decompose complex queries into atomic components and verify each component is addressed in the answer before returning. Use RAGAS Answer Relevancy metric (target: >0.75) with automatic re-generation for scores below threshold. Root cause mitigation: Prevents context-anchoring by explicitly binding answer generation to parsed query intent.
Apply multi-source consensus verification: Require answers synthesized from multiple sources to explicitly cite which sources support each claim and flag unresolved contradictions. Implementation: Use semantic similarity checks across source fragments to detect cherry-picked evidence patterns. Root cause: Ensures balanced representation of evidence when sources conflict.
Enforce comprehensive coverage checks: Implement structured extraction requiring explicit treatment of caveats, limitations, exceptions, and counterevidence for each claim type. Use template responses with mandatory caveat sections. Root cause: Prevents omission of qualifying information that would change user decision-making.
Detection & Response
Answer completeness monitoring: Measure coverage of query intents in generated answers. Track query decomposition rate (% of query components explicitly addressed) and flag responses with coverage <85%. Instrument RAG pipeline to log query-answer similarity scores per component. Alert on sustained scores <0.70.
Evidence balance scoring: For each answer, compute evidence distribution across sources and flag one-sided responses (>70% from single source on multi-source queries). Implement automated extraction of caveat/limitation mentions and track inclusion rates by query type. Target: >80% of medical/financial answers include relevant caveats.
Architecture Patterns
Query Intent Decomposition Graph: Parse complex queries into a DAG of atomic intents before retrieval. Each retrieved document is mapped to specific intent nodes. Answer generation must satisfy all leaf nodes. Validation layer computes coverage before response generation.
Evidence Consensus Engine: Maintain a fact graph where each claim is attributed to specific sources with confidence scores. Multi-source claims require consensus computation (intersection of sources supporting claim). Flagging layer surfaces contradictions to generation model.
Structured Response Templates: Use task-specific response schemas that enforce inclusion of: primary answer, supporting evidence, relevant caveats/exceptions, alternative interpretations, confidence bounds. Auto-flag template violations before user delivery.
Key Metrics
| Metric | Target | Alert Threshold | Measurement Method |
|---|---|---|---|
| Answer Relevancy Score | >0.75 | <0.70 | RAGAS metric on generated answers vs. original query |
| Query Coverage Rate | >90% | <85% | Percentage of query components explicitly addressed in answer |
| Evidence Balance Index | >0.6 | <0.4 | Distribution of citations across sources (Gini coefficient, 0=balanced, 1=single-source) |
| Caveat Inclusion Rate | >80% | <70% | Percentage of medical/financial answers including relevant limitations |
| User Clarification Rate | <5% | >10% | Percentage of answered queries requiring follow-up clarification |
Alerts & Escalation
| Alert | Condition | Severity | Response |
|---|---|---|---|
| Low Answer Relevancy | Answer Relevancy Score < 0.70 for >5% of queries in 1-hour window | HIGH | Page on-call; trigger re-generation with query reinforcement prompt |
| Single-Source Dominance | Evidence Balance Index < 0.4 on multi-source queries for >3 consecutive queries | MEDIUM | Log event; audit cherry-picking patterns in retrieval/synthesis |
| Rising Clarification Demand | User Clarification Rate exceeds 10% (vs. 5% baseline) over 24-hour window | HIGH | Investigate query decomposition or answer template effectiveness |
References
- Avianca Lawyers - 6 fake cases cited
- Stanford Legal RAG Hallucinations - Fabricated legal citations