Three hours into a market research session, you paste the AI’s polished summary into your doc. Sources cited. Statistics clean. Sounds airtight. Then you check one claim against the actual source it mentioned… and the claim isn’t there. The AI didn’t lie on purpose. It filled in the gap with its best guess and wrapped it in confident language. Now your whole report is suspect, and you have no easy way to know which other claims are solid and which ones the model quietly invented.
That’s the problem u/Shamix1948 on r/PromptEngineering got tired of. After weeks of trying to fix AI hallucinations with increasingly complex system prompts, he gave up on prompting better and rethought the architecture entirely. What he built is a Chain of Verification (CoV) loop, and it’s one of the more practical approaches I’ve come across for serious AI-assisted research.
🔍 Why This Actually Matters
Hallucinations don’t happen because the model is dumb. They happen because AI is trained to sound coherent. Ask it to research something, and it produces polished, confident-sounding output even when it’s bridging gaps with guesswork. The bigger and more complex your prompt, the worse the drift gets over time.
One commenter in the thread put it clearly: “Reliability doesn’t come from better prompts, but from enforced verification steps.”
That’s the actual shift here. Stop trying to make the AI smarter through prompting. Build a system that audits its own output before the result reaches you.
🛠 How the CoV Loop Works (Step by Step)
The original poster manages his entire research logic inside a Notion workspace. The loop has three stages, and none of them are optional:
Step 1: Generate the initial research
The AI processes raw data and produces a first draft from whatever sources or inputs you feed it. This might be a pile of URLs, a competitor’s product page, or a set of industry reports you’ve dropped in. Nothing is treated as final at this point. It’s a working document only, explicitly labeled as unverified.
Step 2: Run the self-critique with verification questions
This is the part that actually matters. The AI, given a separate prompt, runs through a structured set of targeted questions:
- Does this source actually support this claim?
- Is this statistic cited directly or inferred?
- Does this conclusion follow logically from the data provided?
- Are there any claims here that the provided sources don’t directly address?
These aren’t vague “does this seem right?” checks. They’re specific questions designed to surface the exact failure modes AI research tends to hit. The critique happens in its own context, not bundled into the generation step.
Step 3: Rewrite only after verification passes
The final output gets written only once the verification step clears. If verification flags an issue, the loop restarts. You don’t get a finished report that hasn’t been audited.
The original poster notes he’s doing this to scale his YouTube and SaaS research while keeping quality tight. For anyone doing research where errors have real consequences, this kind of enforcement isn’t optional.
Quick Start:
What you need: any LLM you’re already using, and somewhere to hold the logic. Notion works for lighter workloads. The original poster also mentions LangGraph and Make.com as options when you need more automation or heavier volume. No coding background required to start with the Notion version.
💡 Tips and Tricks
A few things worth keeping in mind before you build your own version:
- Your verification questions do most of the work. Vague questions produce vague audits. “Does this source support this claim?” is specific. “Does this sound plausible?” is useless. Invest time in writing sharp questions tailored to the type of research you’re doing, whether that’s market analysis, technical summaries, or competitive intel.
- Keep generation and verification in separate prompts. Asking the AI to generate and self-check in one shot undermines the whole point. The critique needs its own dedicated context window.
- Notion is a starting point, not the ceiling. It works well for solo research at moderate volume. Once you’re running this at scale or want it automated, LangGraph or Make.com give you more control.
- Expect this to slow you down. That’s the point. Faster research that’s wrong isn’t research. Build the loop for the work where accuracy actually costs you something if it slips.
🚀 Where to Go From Here
The CoV loop isn’t complicated, but it requires you to stop thinking about AI research as a single-prompt problem and start thinking about it as a system. That’s the mental shift that makes the difference.
Head over to the original r/PromptEngineering thread to read the full discussion, including the community debate on Notion versus LangGraph and some sharp follow-up questions about scaling this approach. Well worth the read if you’re doing any AI-assisted research where mistakes aren’t free!
Frequently Asked Questions
Q: Why is Chain of Verification better than just using complex prompts?
Complex prompts try to solve hallucination through better wording, but the AI still drifts over time. As one commenter noted, “reliability doesn’t come from better prompts, but from enforced verification steps.” CoV works because it forces the AI to audit its own work before finalizing output, it shifts from hoping the AI gets it right to guaranteeing it passes a checkpoint.
Q: Isn’t adding verification loops going to kill my productivity with extra steps?
It might feel slower initially, but you’re trading one extra AI pass for removing entire false research paths. When you catch hallucinations early (before they propagate), you save way more time than you spend on verification. The key is making your verification questions specific and binary so the AI doesn’t waste tokens on debate.
Q: Should I build this in Notion, LangGraph, or Make?
Notion works well if your workflow is lighter and you need transparency in each step, you can literally see the logic running. LangGraph scales better if you’re running this frequently or need to integrate multiple tools. Make sits in the middle if you prefer visual workflows but need more automation than Notion offers.
Q: What makes a good verification question?
Keep them binary and testable: “Does the source actually mention this claim?” or “Is this data from 2025 or later?” Avoid open-ended judgment calls that require the AI to argue with itself. The tighter and more specific your verification, the more reliably it catches real errors.
Beyond Single Prompts: Implementing a Chain of Verification (CoV) loop in Notion for hallucination-free research
by u/Shamix1948 in PromptEngineering