REVIEW 3 cited by
Knowledge Conflicts for LLMs: A Survey
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
This survey provides an in-depth analysis of knowledge conflicts for large language models (LLMs), highlighting the complex challenges they encounter when blending contextual and parametric knowledge. Our focus is on three categories of knowledge conflicts: context-memory, inter-context, and intra-memory conflict. These conflicts can significantly impact the trustworthiness and performance of LLMs, especially in real-world applications where noise and misinformation are common. By categorizing these conflicts, exploring the causes, examining the behaviors of LLMs under such conflicts, and reviewing available solutions, this survey aims to shed light on strategies for improving the robustness of LLMs, thereby serving as a valuable resource for advancing research in this evolving area.
Forward citations
Cited by 3 Pith papers
-
Trust, but Don't Verify: Epistemic Blind Spots in LLM Source Evaluation
LLMs identify fabricated statistics in isolation (rates 0.76-1.00) but ignore numeric validity during synthesis, relying on a methodology-register representation that transfers across domains.
-
Helpful Agent Meets Deceptive Judge: Understanding Vulnerabilities in Agentic Workflows
LLM agents frequently switch correct answers after one round of misleading feedback, and the new WAFER-QA benchmark measures this with web-backed critiques.
-
Scaling laws for activation steering with Llama 2 models and refusal mechanisms
Activation steering with contrastive vectors becomes less effective as Llama 2 models scale from 7B to 70B parameters, with peak effect at roughly 40% of the model's layers.
Discussion (0). Continue with ORCID to comment.