Beyond Logprobs: A Multi-Signal Confidence Engine for LLM-Based Document Field Extraction
This paper introduces ExtractConf, a cross-domain confidence engine that significantly improves the reliability of LLM-based document field extraction by fusing signals from two structurally distinct extraction strategies (a field-guided "Hunter" and a document-guided "Mapper") with image and layout features to effectively distinguish trustworthy extractions from hallucinations, thereby enabling safe human-in-the-loop automation.
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 running a busy factory that processes thousands of business documents every day, like invoices and receipts. You've hired a super-smart AI robot (an LLM) to read these documents and pull out specific numbers, like "Total Amount" or "Tax ID."
The problem? Sometimes, the robot makes a mistake. It might confidently write down a number that doesn't exist, or it might read a smudge on the paper as a zero. In a high-stakes factory, a "silent mistake" (where the robot gives a wrong answer but acts like it's sure) is worse than the robot just saying, "I can't read this."
This paper introduces a new system called EXTRACTCONF. Think of it not as a better reader, but as a super-smart quality control inspector that stands next to the robot to decide: "Can we trust this answer, or should we send it to a human to check?"
Here is how it works, broken down into simple concepts:
1. The "Two-Headed" Strategy (Hunter vs. Mapper)
Most systems ask the AI one question: "What is the Total Amount?" If the AI guesses, it might be wrong.
EXTRACTCONF asks the AI to read the document twice, but in two completely different ways:
- The Hunter: This is like a detective looking for a specific suspect. It is told, "Find the 'Total Amount' field." Because it is under pressure to find that specific slot, it might accidentally "hallucinate" (make up) a number if the field is blurry or missing.
- The Mapper: This is like a tourist looking at a map. It is told, "Scan the whole document and tell me what important numbers you see." It only reports what it actually sees. If the "Total Amount" is missing or blurry, the Mapper stays silent.
The Magic: If the Hunter says "The total is $500" but the Mapper says "I don't see a total," the system knows something is wrong. If they both agree on "$500," the system feels much more confident. This "disagreement" is a huge clue that the paper is hard to read or the answer is tricky.
2. Looking at the Paper, Not Just the Robot
The paper argues that the robot's confidence (how sure it feels) is often a lie. If the paper is blurry, the robot might still feel very confident about the wrong answer.
So, EXTRACTCONF doesn't just listen to the robot. It also checks:
- The "Camera" (OCR): How clear is the text on the actual image? If the camera sees a smudge, the system knows the answer is risky, even if the robot says it's 100% sure.
- The "Map" (Spatial Layout): Where did the robot look? If the Hunter looked at the top-left corner and the Mapper looked at the bottom-right, they are looking at different things. That's a red flag.
- The "Texture" (Image Quality): Is the specific area of the paper where the number should be blurry or faded?
3. The Final Verdict
All these clues (the two different readings, the camera quality, the location, and the robot's internal confidence) are fed into a traffic light system.
- Green Light: The robot and the inspector agree, the paper is clear, and the location makes sense. Automate it! (Send it to the computer).
- Red Light: The robot and inspector disagree, or the paper is blurry. Stop! (Send it to a human to check).
What Did They Find?
The researchers tested this on thousands of real invoices. Here is what happened:
- Old Way: If they just trusted the robot's "confidence score," the system would try to automate almost everything, including the mistakes. It was like a traffic light that was stuck on green.
- New Way (EXTRACTCONF): By using the "Two-Headed" strategy and checking the paper quality, they could filter out the bad answers.
- When they let the system automate the "Green Light" answers, 99.1% of them were correct.
- Without this system, the robot was only correct about 73.3% of the time.
- They reduced the risk of making a mistake by 70% compared to the old methods.
The "Zero-Shot" Surprise
The coolest part is that they trained this system on invoices, and then tested it on receipts (a totally different type of paper) without teaching it anything new. It worked just as well. This proves that the system isn't just memorizing what an invoice looks like; it's actually learning how to tell if any document is hard to read.
In a Nutshell
EXTRACTCONF is a safety net. It doesn't try to make the AI smarter at reading; instead, it builds a smarter judge that knows when the AI is guessing and when it's actually seeing the truth. It saves money by automating the easy stuff and sending the tricky stuff to humans, ensuring that no wrong numbers slip through the cracks.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.