DRAGged into Conflicts: Detecting and Addressing Conflicting Sources in Search-Augmented LLMs

Arie Cattan, Alon Jacovi, Ori Ram, Jonathan Herzig, Roee Aharoni +4 more
6/10/2025
cs.CLcs.AIcs.LG

No official code found. Best implementation: google-research-datasets/rag_conflicts (15 stars, Apache-2.0, last commit 2025-06-11).

Abstract

Retrieval Augmented Generation (RAG) is a commonly used approach for enhancing large language models (LLMs) with relevant and up-to-date information. However, the retrieved sources can often contain conflicting information and it remains unclear how models should address such discrepancies. In this work, we first propose a novel taxonomy of knowledge conflict types in RAG, along with the desired model behavior for each type. We then introduce CONFLICTS, a high-quality benchmark with expert annotations of conflict types in a realistic RAG setting. CONFLICTS is the first benchmark that enables tracking progress on how models address a wide range of knowledge conflicts. We conduct extensive experiments on this benchmark, showing that LLMs often struggle to appropriately resolve conflicts between sources. While prompting LLMs to explicitly reason about the potential conflict in the retrieved documents significantly improves the quality and appropriateness of their responses, substantial room for improvement in future research remains.

View on arXivView PDF

Code Implementations(1)

Apache-2.0

CONFLICTS is a QA dataset annotated with knowledge conflict types. Each instance comprises a query, a set of retrieved relevant passages, a corresponding conflict type label, and, for specific types, the ground truth correct answer

152Jun 5, 20251 years agoApache-2.0

Similar Papers

Cite this paper

@article{cattan2025dragged,
  title  = {DRAGged into Conflicts: Detecting and Addressing Conflicting Sources in Search-Augmented LLMs},
  author = {Arie Cattan and Alon Jacovi and Ori Ram and Jonathan Herzig and Roee Aharoni and Sasha Goldshtein and Eran Ofek and Idan Szpektor and Avi Caciularu},
  year   = {2025},
  eprint = {2506.08500},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2506.08500v2}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2506.08500.svg)](https://codeofpaper.com/paper/2506.08500)

Discussion