Context Ignored

Issue: Model Ignores Retrieved Context

Frequency: Common

Symptoms

• Answer doesn’t use information from retrieved documents
• Generic response when specific info was available
• Model responds from parametric knowledge instead
• Context provided but not reflected in answer

Root Cause

• Prompt doesn’t emphasize context usage
• Context buried in long prompt
• Model attention focuses elsewhere
• Context format not conducive to extraction

Example

Retrieved context:
"Our return policy allows returns within 30 days. Items must be 
unopened and in original packaging. Refunds are processed within 
5-7 business days."

Query: "What's your return policy?"

Agent response: "Most retailers offer a 30-60 day return window. 
You should check the specific store's policy for details."

Reality: Specific policy was in context but ignored

Result: Generic unhelpful answer instead of specific policy

Mitigation Strategies

1. Context-first prompting: Place context prominently, instruct to use it
2. Extractive grounding: Require quotes from context
3. Context highlighting: Format context to draw attention
4. Instruction emphasis: Explicitly say “Answer ONLY from the context”
5. Answer validation: Verify answer references context content
6. Attention visualization: Debug which context parts model attends to

Detection

• Track context utilization rate
• Compare answer to context overlap
• Monitor generic vs. specific response rates
• Flag answers without context references

Mitigation Strategies

Prevention

1. 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.

2. 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.

3. 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

1. 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.

2. 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

1. 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.

2. 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.

3. 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

Alerts & Escalation

References

• Medium: 7 RAG Hallucination Root Causes - Context utilization failures
• Self-Healing RAG Layer - Fixing context issues