← Latest papers
💬 NLP

Detection and Interpretability Analysis of Quotation Errors by Large Language Models

This paper proposes an automated framework for detecting quotation errors using fine-tuned large language models enhanced with full-text data integration, demonstrating that incorporating source abstracts yields optimal performance while providing interpretability analysis of the model's predictions.

Original authors: Bei Huang, Yingyi Zhang, Shenghao Huang, Chengzhi Zhang

Published 2026-06-09
📖 5 min read🧠 Deep dive

Original authors: Bei Huang, Yingyi Zhang, Shenghao Huang, Chengzhi Zhang

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 are a librarian in a massive, bustling library of scientific knowledge. Every day, scholars write new books (research papers) and point to old books (citations) to back up their claims. Usually, they say, "As Author X said in their book, the sky is blue."

But sometimes, a scholar gets it wrong. Maybe they say, "Author X said the sky is green," even though Author X never said that. Or maybe they say Author X proved something, but Author X actually said the exact opposite. This is what the paper calls a "quotation error." It's like a game of "telephone" where the message gets distorted, leading to confusion and unfair judgments in the academic world.

The problem is that there are too many books and too many scholars for humans to check every single quote manually. It would take forever! So, the authors of this paper asked: Can we teach a super-smart computer (a Large Language Model or LLM) to spot these lies and mistakes automatically?

Here is how they tried to teach the computer, explained through simple analogies:

1. The "Schooling" vs. "Reading the Manual" Approach

The researchers tested two ways to teach the computer:

  • The "Reading the Manual" Approach (Prompting): They gave the computer a specific instruction (a prompt) like, "Here is a quote and the original book. Tell me if the quote is true." They tried this with different versions of the computer, asking it to solve the problem just by reading the instructions.
  • The "Schooling" Approach (Fine-Tuning): Instead of just giving instructions, they took a pre-trained computer and gave it a special "boot camp" (fine-tuning). They fed it thousands of examples of correct and incorrect quotes so it could learn the patterns deeply, adjusting its internal "brain" to become an expert at this specific task.

The Result: The "Schooling" approach worked much better. It was like taking a student who knows how to read and giving them a specialized test prep course; they suddenly became much better at spotting the specific errors than just reading the instructions.

2. The "Abstract" vs. "Full Book" Dilemma

When checking a quote, do you need to read the whole book, or is the summary (abstract) enough?

  • The Abstract: This is like reading the back cover of a book. It gives you the main idea.
  • The Full Text: This is reading every single chapter.

The researchers tried three ways to feed the computer the "Full Text":

  1. The "Relevant Snippet" Method: They scanned the whole book and only picked the 10 sentences that sounded most like the quote.
  2. The "Source Summary" Method: They scanned the whole book and picked the 10 sentences that sounded most like the book's summary (abstract).
  3. The "Dump" Method: They just threw the entire book into the computer's memory.

The Result: Surprisingly, the "Source Summary" method worked best. It was like finding the perfect "cheat sheet" of relevant sentences that matched the book's main theme. Just dumping the whole book (too much information) or picking random snippets didn't work as well as picking the sentences that best reflected the book's core message.

3. The "Why" Behind the Answer (Interpretability)

When the computer says, "This quote is wrong," we need to know why. Did it guess? Did it see a specific word?
The researchers used a tool called TokenSHAP. Think of this as a highlighter pen for the computer's brain.

  • It looks at every single word (token) in the quote and the original text.
  • It highlights words in Red if they helped the computer decide the quote was wrong.
  • It highlights words in Blue if they made the computer think the quote was right (or confused it).

The Result: This showed that the "Schooling" (fine-tuned) computer was actually looking at the right things. It noticed subtle contradictions (like "increases" vs. "decreases") that the untrained computer missed. The untrained computer often just saw similar words (like "sky" and "blue") and guessed "True," while the trained computer saw the logic was broken.

4. Where the Computer Still Stumbles

Even with the "Schooling," the computer isn't perfect. The researchers found four main reasons it still makes mistakes:

  • Missing Background Knowledge: If a quote relies on a fact everyone knows (like "the UK has a certain population size") but the book doesn't explicitly state it, the computer gets confused.
  • Math Trouble: If a quote changes units (like "75 nmol" vs. "75 micromol"), the computer sometimes misses the difference.
  • Big vs. Small Numbers: It sometimes confuses "the biggest increase" with "the biggest total number."
  • Missing Conditions: It might miss a tiny "if" or "only" in the sentence that changes the whole meaning.

The Bottom Line

This paper is essentially a guide on how to build a better "Quote Police" for science. They found that:

  1. Training the AI specifically on this task works better than just asking it nicely.
  2. Feeding it the right parts of the full text (specifically sentences that match the book's main theme) helps it see the truth better than just reading the summary or the whole book.
  3. We can see why the AI makes decisions, which helps us trust it more and fix its mistakes.

The goal isn't to replace human scholars, but to give them a powerful tool to catch the "telephone game" errors before they spread through the academic community.

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 →