← Latest papers
💬 NLP

Stress Testing Factual Consistency Metrics for Long-Document Summarization

This paper systematically evaluates six reference-free factual consistency metrics on long-document summarization, revealing their significant limitations in handling long-range dependencies and information-dense claims through a series of factuality-preserving perturbations, while proposing specific directions for future improvements.

Original authors: Zain Muhammad Mujahid, Dustin Wright, Isabelle Augenstein

Published 2026-04-30
📖 5 min read🧠 Deep dive

Original authors: Zain Muhammad Mujahid, Dustin Wright, Isabelle Augenstein

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you have a very long, complicated book—maybe a legal contract, a scientific paper, or a fantasy novel. You ask a smart computer (an AI) to write a short summary of it. The summary sounds smooth and professional, but did the computer actually tell the truth, or did it make things up?

This paper is like a "stress test" for the tools we use to check if those summaries are true. The authors, Zain Muhammad Mujahid, Dustin Wright, and Isabelle Augenstein, wanted to see if the current "truth detectors" work well when the source material is huge and complex.

Here is the breakdown of their findings using simple analogies:

The Problem: The "Short-Story" Detectors

Currently, we have several automatic tools (metrics) designed to check if a summary is factual. Think of these tools as security guards at a museum.

  • The Issue: These guards were trained on small, simple paintings (short documents).
  • The Challenge: Now, we are asking them to guard a massive, sprawling cathedral with thousands of stained-glass windows (long documents). The authors suspected these guards might get confused, miss details, or panic when the building is too big.

The Experiment: The "Shape-Shifting" Test

To test these guards, the researchers didn't just look at the summaries; they played tricks on them. They took a summary that was 100% true and made small, harmless changes to it, like a magician changing a card's color without changing its value.

They used seven different tricks:

  1. Paraphrasing: Rewriting sentences in different words.
  2. Simplifying: Making complex sentences easier to read.
  3. Synonym Swap: Replacing words with their synonyms (e.g., "big" to "huge").
  4. Negation: Flipping the logic (e.g., "It is not the case that he didn't go" instead of "He went").
  5. Compression: Making the summary even shorter.
  6. Vocabulary Reduction: Using fewer, simpler words.
  7. Adding Noise: Inserting a random true sentence from the original book that doesn't fit the summary's main point.

The Goal: If a truth detector is good, it should give the same score to the original summary and the tricked version, because the facts haven't changed. If the score jumps up and down wildly, the detector is unreliable.

The Results: The Guards Are Stumbling

The researchers tested six popular truth detectors across three types of long documents: Science Fiction (stories), Legal (court rulings), and Scientific (research papers).

Here is what they found:

1. The "Surface-Level" Trap
Most of the detectors are easily fooled by surface changes.

  • Analogy: Imagine a guard who only checks if a person is wearing a red hat. If you swap the red hat for a blue one (even if it's the same person), the guard says, "Not allowed!"
  • Finding: When the researchers changed the wording or simplified the sentences, the detectors gave wildly different scores. Some detectors hated legal language; others struggled with scientific jargon. They were reacting to how the words looked, not what they meant.

2. The "Needle in a Haystack" Problem
Long documents have information scattered everywhere.

  • Analogy: If you are looking for a specific fact in a 500-page book, a short summary might pull that fact from page 10, page 200, and page 400.
  • Finding: The detectors struggled when a summary sentence relied on information from many different parts of the book. They got confused when the evidence was "entangled" or spread out. They worked better when the evidence was right next to each other.

3. The "Context Window" Issue
To check a summary sentence, the detectors need to look at the original text.

  • Analogy: Imagine trying to understand a joke by reading only the punchline. You need the setup (the context) to get it.
  • Finding: When the researchers gave the detectors a wider "view" of the original text (more context), some detectors got better at their job. However, even with more context, none of them were perfect. Some detectors (like SummaC) seemed to ignore the extra context entirely, sticking to their narrow view.

4. The "Legal" vs. "Story" Difference

  • Legal Text: The detectors were most unstable here. Legal language is precise and logical. Changing a single word or structure (like a negation) threw the detectors into a panic.
  • Science Fiction: The detectors were slightly more stable but still inconsistent.
  • Scientific Papers: Interestingly, when the summary came from multiple documents, the detectors were more stable. It seems having redundant information (the same fact repeated in different papers) helped the detectors feel more confident.

The Conclusion: We Need Better Tools

The paper concludes that the current "truth detectors" are brittle. They are like a scale that gives you a different weight every time you step on it, even if you haven't moved.

  • They fail when the summary is rephrased.
  • They fail when the facts are spread out across a long document.
  • They fail when the logic gets complex (like double negatives).

The Takeaway: We cannot trust these tools to automatically verify long summaries yet. To fix this, we need new tools that can:

  1. Reason across the whole book (not just look at one sentence at a time).
  2. Understand the meaning regardless of how the words are arranged.
  3. Handle the "messiness" of long, complex documents without getting confused.

The authors have released their code and data so others can try to build these better, more robust detectors.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →