How Far Can You Get Without a GPU? A Systematic Benchmark of Lightweight Hallucination Detection Across Question Answering, Dialogue, and Summarisation
This paper systematically benchmarks five lightweight, CPU-feasible hallucination detection methods across question answering, dialogue, and summarization tasks, revealing that performance is highly task-dependent with ensemble methods excelling in QA, NLI detectors leading in dialogue, and all approaches failing significantly on summarization.
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 by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you have a very smart, chatty robot that can write stories, answer questions, and summarize books. But this robot has a bad habit: sometimes, it makes up facts that sound perfectly real but are completely wrong. This is called a "hallucination."
In the world of AI, catching these lies usually requires a supercomputer (a powerful GPU) or paying for expensive cloud services. But what if you only have a standard laptop? Can you still catch the robot lying?
That's exactly what this paper investigates. The researchers acted like detectives, testing five different "low-tech" tools that run on a regular laptop CPU to see how well they can spot the robot's lies. They tested these tools on three different jobs the robot does: answering questions, having a conversation, and summarizing long documents.
Here is what they found, explained with some everyday analogies:
The Five Detectives
The researchers didn't invent new tools; they used five existing, lightweight methods that anyone can run on a basic computer:
- ROUGE-L: Like a "word-count checker." It just looks at how many words the robot used that match the original source.
- Semantic Similarity: Like a "vibe check." It uses math to see if the meaning of the robot's answer feels similar to the source, even if the words are different.
- BERTScore: A smarter "word-count checker" that understands context, not just exact matches.
- NLI (Natural Language Inference): The "logic detective." It asks, "If the source is true, does this answer have to be true?" If the answer is "No, that doesn't follow," it flags a lie.
- The Ensemble: A "team effort" where the Logic Detective and the Vibe Check combine their scores to make a final decision.
The Three Jobs (and How the Detectives Performed)
1. The Question Answering Job (The Easy Win)
The Scenario: The robot is given a short text and asked a specific question.
The Result: This was the easiest job. The Team Effort (Ensemble) was the star player. By combining the "vibe check" and the "logic detective," it caught about 79% of the lies correctly.
The Takeaway: If you are using a laptop to check answers to specific questions, you don't need a supercomputer. A simple combination of existing tools works very well.
2. The Conversation Job (The Tricky Middle Ground)
The Scenario: The robot is having a back-and-forth chat.
The Result: This got harder. The Logic Detective (NLI) became the best solo performer. It was good at spotting when the robot's reply didn't logically follow from the conversation history. However, the overall success rate dropped compared to the question-answering task.
The Takeaway: In a chat, the robot can weave a lie that sounds like it fits the conversation flow. The logic detective is still your best bet, but it's not as perfect as it was for simple questions.
3. The Summarization Job (The Total Failure)
The Scenario: The robot is asked to summarize a long document into a short paragraph.
The Result: This is where the paper delivers a harsh reality check. Every single tool failed. They performed no better than a coin flip (random guessing).
Why? Imagine trying to find a single typo in a 50-page book by only reading the first 3 pages. That's what happened here. The robot's lies were tiny, subtle factual errors hidden inside a long, mostly correct summary. The lightweight tools were too "short-sighted" to see the whole picture. They got distracted by the fact that the summary mostly looked like the original text, so they missed the small lies.
The Takeaway: If you are trying to check summaries on a laptop without a GPU, don't bother. The current lightweight tools simply aren't powerful enough to handle this specific task.
The Bottom Line
The paper concludes that "how far you can get without a GPU" depends entirely on what you are trying to do:
- Checking Answers? You're good to go. The tools work great.
- Checking Chats? You can do it, but it's harder, and you need the logic-based tools.
- Checking Summaries? You are stuck. The tools break down completely.
The researchers emphasize that this isn't a failure of one specific tool, but a structural limit of lightweight detection. To catch lies in long summaries, you need the heavy machinery (GPUs) or much more complex methods that can read the whole document at once. Until then, if you are working on a budget laptop, you have to know exactly where your tools work and where they will fail.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.