Does RAG Know When Retrieval Is Wrong? Diagnosing Context Compliance under Knowledge Conflict

· Source: cs.CL updates on arXiv.org · Field: Technology & Digital — Artificial Intelligence & Machine Learning · Depth: Expert, extended

Summary

A new diagnostic framework, Context-Driven Decomposition (CDD), has been introduced to analyze how Retrieval-Augmented Generation (RAG) models handle knowledge conflicts between retrieved context and their internal parametric knowledge. CDD is an inference-time probe that elicits separate contextual and parametric answers, compares them, isolates conflicting premises, and records the resolution trace. This framework was tested across Epi-Scale stress tests, TruthfulQA misconception injection, and cross-model reruns on Gemini-2.5-Flash and Claude Haiku/Sonnet/Opus. The study found that standard RAG can exhibit a "Context-Compliance Regime" where retrieved context dominates even when incorrect, achieving only 15.0% accuracy on TruthfulQA misconception injection. CDD significantly improved robustness, reaching 71.3% on temporal shifts and 69.9% on distractor evidence, and its adversarial accuracy gains transferred across model families, though the causal coupling mechanism varied.

Key takeaway

For AI Architects and Research Scientists evaluating RAG system robustness, this research indicates that standard RAG can be highly susceptible to misinformation in retrieved contexts. Implementing Context-Driven Decomposition (CDD) can significantly improve accuracy and robustness under knowledge conflict, particularly against explicit factual manipulations and temporal shifts. You should consider integrating CDD's diagnostic approach to understand and mitigate context-compliance issues in your RAG deployments, especially when dealing with potentially stale or adversarial external knowledge sources.

Key insights

CDD diagnoses RAG's handling of knowledge conflicts, revealing context compliance and improving robustness across models.

Principles

Method

CDD uses a five-step reasoning trace: contextual extraction, parametric extraction, divergence check, premise isolation, and conflict resolution to make implicit conflict-resolution observable.

In practice

Topics

Best for: Research Scientist, AI Architect, AI Engineer, AI Scientist, Machine Learning Engineer, MLOps Engineer

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by cs.CL updates on arXiv.org.