Apply to my task
arXiv:2511.08916 ★ 92 Nov 12, 2025

HalluClean: A Four-Step Hallucination Check for LLM Answers

Key result

Ask an LLM to check its own answer for errors and it misses 67% of hallucinations. Ask point-blank 'is anything inaccurate here?' and the model answers superficially, like an expert asked in passing. HalluClean lets you detect hallucinations in already generated text: fact-checking answers, summaries and dialogues. The trick: split the check into 4 explicit steps. The model first drafts a verification plan (what and how it will check), then executes it step by step with reasoning, delivers a verdict and fixes the problem spots. F1 accuracy rises from 33% to 68% on the same GPT-3.5.

HalluClean: A Four-Step Hallucination Check for LLM Answers

HalluClean: A Four-Step Hallucination Check for LLM Answers

02

TL;DR

HalluClean is a prompting technique for detecting and fixing hallucinations in LLM answers. The idea: instead of asking point-blank "is there a mistake here?", the model goes through four explicit steps: it drafts a verification plan, carries it out step by step, delivers a verdict and fixes the problem spots. It all works in a single conversation with no external sources.

The core problem: when you ask an LLM directly to check a text for errors, it often misses inaccuracies. Asked point-blank "is there a hallucination?", GPT-3.5 catches only 33% of errors in question answering. The model "looks" but doesn't "analyze", like someone skimming a text and missing the catch.

How it fixes this: HalluClean makes the model first draft a verification plan (what exactly to check?), then execute it step by step (showing its reasoning), and only then draw a conclusion. On top of that there's a "task router": a short instruction telling the model what it's checking (an answer to a question, a summary, a dialogue). The result: F1 rises from 33% to 68% on the same GPT-3.5.

Want this for your own case? Apply this study to your task: AI adapts its method to what you are working on and writes the prompt.

03

Method Blueprint

STEP 1: PLAN → "What I'll check and how"
    ↓
STEP 2: EXECUTION → Step-by-step analysis with reasoning
    ↓
STEP 3: VERDICT → "Yes, there's a hallucination" / "No"
    ↓
STEP 4: CORRECTION → Rewrite the problem spots (if needed)

💡 All 4 steps run sequentially in ONE conversation
04

Example in Practice

Task: You're a marketer and ChatGPT gave you a competitor profile for an analytics report. You need to check whether the model made up any details.

Prompt:

You are checking a text for factual errors and hallucinations.

TEXT TO CHECK:
"Etsy was founded in 2003 by Rob Kalin. The company was the first in the US to launch a marketplace for handmade goods, in 2010, and today ranks second in sales after Amazon."

STEP 1: Draft a verification plan. Which facts need to be verified? What could the sources of error be?

STEP 2: Carry out the plan step by step. Check each fact and show your reasoning.

STEP 3: Draw a conclusion: does the text contain hallucinations? Yes or No.

STEP 4: If yes, rewrite the text with the errors fixed.

Result: The model will produce a structured analysis: first the plan (check the founding date, the founder's name, the marketplace claim, the market position), then a step-by-step check of each fact with reasoning, then a verdict naming the specific errors, and finally a corrected version of the text.

05

Why It Works

The LLM weakness: asked directly "is there a mistake?", the model gives a superficial answer. It doesn't decompose the task; it just generates the first thing that comes to mind. It's like asking an expert in passing: they'll say something, but they won't think it through.

The LLM strength: models are great at following step-by-step instructions. Tell one "first draft a plan, then execute it" and it really does structure its work. Each step becomes an "anchor" for the next.

How the method exploits this: HalluClean adds a metacognitive layer: the model first thinks about HOW to check, and only then checks. Plus the "task router", a short phrase like "You are checking an answer to a question", helps the model understand the context. The researchers showed that adding the router alone improves F1 on summarization from 25% to 60%.

Control levers:

  • Plan detail: for simple checks "what to check" is enough; for complex ones, add "what sources of error are possible"
  • Reasoning depth: you can ask it to "show the reasoning briefly" to save tokens
  • Task type in the router: "an answer to a question", "a document summary", "a reply in a dialogue"; adjust it to the context
06

Prompt Template

You are checking {content_type} for factual errors and hallucinations.

{CONTENT_TYPE} TO CHECK:
{text_to_check}

STEP 1: Draft a verification plan. Which facts need to be verified? What could the sources of error be?

STEP 2: Carry out the plan step by step. Check each fact and show your reasoning.

STEP 3: Draw a conclusion: does the text contain hallucinations? Yes or No.

STEP 4: If yes, rewrite the text with the errors fixed.

Placeholders:

  • {content_type}: what you're checking: "an answer to a question", "a document summary", "a reply in a dialogue", "a product description"
  • {text_to_check}: the text that needs checking

Router Variants by Task Type

TaskRouter
QA"You are checking an answer to a question"
Summary"You are checking whether the summary matches the source document"
Dialogue"You are checking whether the reply is consistent with the dialogue history"
Math"You are checking whether the problem is solvable under the given conditions"
07

Limitations

⚠️ Depends on the base model: the method amplifies a model's abilities but doesn't create new ones. If GPT-3.5 doesn't know a fact, it can't check it. For fact-checking in specialized fields (medicine, law), combine it with web search.

⚠️ Three types of errors remain: (1) language misunderstanding: the model misreads the question, (2) missing knowledge: the model doesn't know the fact it needs, (3) reasoning errors: it understood correctly but drew the wrong conclusion.

⚠️ More tokens: the four-step process generates more text than a direct question. For bulk checking, factor in the cost.

08

How They Studied It

A team from the Harbin Institute of Technology tested HalluClean on five task types: question answering, dialogue, summarization, math problems and self-contradictions. They used four existing labeled benchmarks, about 2,000 examples in total, balanced between "hallucination / no hallucination".

They compared it with the direct question "is there a hallucination?" and with other prompting methods: Step-by-Step, Plan-and-Solve, SelfCheckGPT, ChatProtect. They tested on five models: GPT-3.5, GPT-4o-mini, Llama-3-70B, DeepSeek-V3, DeepSeek-R1.

Main insight: the direct question gives an F1 of about 33% on QA, while HalluClean gives 68% on the same GPT-3.5. Interestingly, each component contributes something. The task router alone lifts summarization F1 from 25% to 60%. Adding structured reasoning brings it to 66%. The effect is additive, not a single silver bullet.

They also tested it on domain-specific tasks (medicine, finance), where the method works even better: F1 rose from 9% to 92% on CovidQA. That makes sense: in specialized fields models make things up even more often, so structured checking catches more.

09

Original from the Paper

Context: The four-step prompt for the Question Answering task (verbatim from the paper):

Step-1: You are provided with a question and its corresponding answer.
Your task is to determine whether the answer contains hallucinated content.
Let's understand the task and devise a plan to solve the task.
[Task Input]

Step-2: Let's carry out the plan and solve the task step by step.
Show the reasoning process.
[Task Input; Result from Step-1]

Step-3: Please conclude whether the answer contains hallucinated content
with Yes or No.
[Task Input; Result from Step-2]

Step-4: Given a question, its corresponding hallucinated answer, and an
analysis explaining why the answer contains hallucinated content.
Your task is to answer the question without introducing any hallucinations.
[Task Input; Result from Step-2]

Task routers (verbatim):

Task TypeTask Routing Prompt
Question AnsweringYou are provided with a question and its corresponding answer. Your task is to determine whether the answer contains hallucinated content.
Dialogue SystemsYou are provided with a dialogue history and its corresponding response. Your task is to determine whether the response contains hallucinated content.
SummarizationYou are provided with a document and its corresponding summary. Your task is to determine whether the summary contains hallucinated content.
10

Adaptations and Extrapolations

💡 Adaptation: checking your own writing before you send it

The method works not only for checking LLM answers but also for self-checking, when you wrote a text yourself and want to catch the errors:

You are a fact-checking editor. Check my text for factual errors.

MY TEXT:
{your_text}

STEP 1: Which facts in the text can be checked? List the claims.

STEP 2: Check each claim. Show your reasoning.

STEP 3: Which claims are definitely correct, which are doubtful, which are wrong?

STEP 4: Suggest fixes for the doubtful and wrong ones.

🔧 Technique: add web search for fact-checking

The researchers showed that HalluClean + retrieval gives an F1 of 80% instead of 68%. In a chat with Claude or ChatGPT:

You are checking an answer to a question for hallucinations.
When checking facts, search the web.

QUESTION: {question}
ANSWER: {answer}

STEP 1: Which facts need to be checked via search?
STEP 2: Find the information and compare it with the answer.
STEP 3: Verdict: is there a hallucination? Yes/No.
STEP 4: If yes, fix it.

🔧 Technique: shorten it for simple checks

If you're checking something simple (a date, a name, a single number), you can drop the detailed plan:

Check this fact: {claim}

Show your reasoning and give a verdict: true or not?
If not, correct it.
11

Resources

Paper: "HalluClean: A Unified Framework to Combat Hallucinations in LLMs"
Authors: Yaxin Zhao, Yu Zhang, Harbin Institute of Technology, Harbin, China
Code: https://github.com/tingmuor/HalluClean
Benchmarks: HaluEval, UMWP, ChatProtect, HaluBench


Research digest

Key result

Ask an LLM to check its own answer for errors and it misses 67% of hallucinations. Ask point-blank 'is anything inaccurate here?' and the model answers superficially, like an expert asked in passing. HalluClean lets you detect hallucinations in already generated text: fact-checking answers, summaries and dialogues. The trick: split the check into 4 explicit steps. The model first drafts a verification plan (what and how it will check), then executes it step by step with reasoning, delivers a verdict and fixes the problem spots. F1 accuracy rises from 33% to 68% on the same GPT-3.5.

Principle

Don't ask 'is there a mistake?'; make the model structure the check. The process: 1. Plan → the model thinks about WHAT to check and HOW 2. Execution → step-by-step analysis with explicit reasoning 3. Verdict → yes/no, is there a hallucination 4. Correction → rewrite the problem spots Add a router: one line like 'You are checking an answer to a question'. The model gets the context and knows what to pay attention to. Without a router, the model doesn't understand WHAT exactly to check: facts in a summary, logic in a dialogue or the accuracy of an answer.

Why it works

The direct question 'is there a mistake?' makes the model generate the first thing that comes to mind. With no time to think, it gives a superficial answer. A step-by-step structure creates anchors for reasoning. Each step is a stopping point. The model can't jump straight to the conclusion; it has to draft a plan first, then execute it. That's a metacognitive layer: the model thinks about HOW to check rather than just checking. Adding the router 'You are checking a summary' alone improves F1 from 25% to 60% on summarization: the model understands it should look for discrepancies with the source text rather than just 'check for errors'.

When to apply

Checking content after generation → specifically fact-checking answers to questions, checking summaries against the source document, validating replies in a dialogue, especially when you're working without external sources (RAG, web search). NOT a fit for specialized fields (medicine, law, narrow technical topics): if the model doesn't know a fact, it can't check it. In those cases, combine it with web search.

Mini recipe

1. Set the router for the task type: `You are checking an answer to a question` (for QA), `You are checking whether the summary matches the source document` (for summarization), `You are checking whether the reply is consistent with the dialogue history` (for chatbots) 2. Provide the text to check: copy the model's answer or the generated content 3. Spell out the 4 steps: - STEP 1: `Draft a verification plan. Which facts need to be verified?` - STEP 2: `Carry out the plan step by step. Check each fact and show your reasoning` - STEP 3: `Draw a conclusion: does the text contain hallucinations? Yes or No` - STEP 4: `If yes, rewrite the text with the errors fixed` 4. Get a structured analysis: the model returns the plan, the step-by-step check, the verdict and a corrected version

Examples

[BAD]: `Check this text for errors: [text]. Are there any inaccuracies?` The model gives a superficial answer and misses 60-70% of hallucinations [GOOD]: `You are checking a product description for factual errors. TEXT TO CHECK: "The iPhone 15 came out in September 2022 with the A16 chip and USB-C support" STEP 1: Draft a verification plan. Which facts need to be verified? STEP 2: Carry out the plan step by step. Check each fact and show your reasoning. STEP 3: Draw a conclusion: does the text contain hallucinations? Yes or No. STEP 4: If yes, rewrite the text with the errors fixed` The model drafts a plan (check the release date, the chip model, the port type), finds the date error (the iPhone 15 came out in 2023, not 2022) and returns a corrected version

In plain words

The point is that LLMs are, by nature, compulsive liars who believe their own nonsense. When you ask a model point-blank, "Did you make anything up here?", it just gives you a shallow "no", because it can't be bothered to dig through its own hallucinations. HalluClean breaks that habit by making the model work not like a storyteller but like a meticulous detective who first plans the interrogation and only then delivers the verdict.

It's like asking a sleepy student to proofread a thesis. If you just ask, "All good?", they'll nod and doze off again. But if you make them first list every formula, then recompute each one on a calculator, and only at the end sign off on the result, the odds of missing a blunder drop dramatically. HalluClean is exactly that mandatory checklist that keeps the model from "breezing through" a tricky spot on autopilot.

The method runs as a strict four-step drill in one chat: first drafting a plan (what exactly we're checking), then step-by-step execution, then a clear verdict, and only at the end fixing the screw-ups. The beauty of it is that the model catches itself red-handed while reasoning. Make it spell out the verification logic point by point, and it suddenly "notices" that the fact it invented about a competitor or a software feature that doesn't exist is total garbage that doesn't square with reality.

Although the method was tested on hallucinations, this principle of forced decomposition applies to any complex task. Whether it's writing code, a legal audit or building a marketing strategy, making the LLM draft a verification plan first and then follow it sends answer quality through the roof. Direct questions don't work; only structured interrogation does. It turns the model from an unsure daydreamer into a reliable tool you can trust with fact-checking.

Bottom line: stop counting on the model's honesty; it will always try to cut corners. Use HalluClean to knock the nonsense out of the model with four stages of checking. Either you make it work step by step, or you get a report full of pretty but utterly useless fiction. One prompt, four steps, and the risk of hallucinations drops to a minimum while your competitors keep believing whatever their chatbot "hallucinated" for them.

AI lab assistant

Apply this study to your task

Describe what you're working on. AI takes the method and the measured results from this paper and adapts them to your case, or writes a ready prompt built on them.

Based on HalluClean: A Four-Step Hallucination Check for LLM Answers arXiv:2511.08916

Sign in to apply this study New accounts get 50 free credits.

Get the week’s best papers by email

One email on Sundays with the highest-rated new techniques. Unsubscribe with one click.