Rendered at 13:23:34 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
RugnirViking 3 hours ago [-]
a clearly LLM written piece about how frontier models are struggling to get past 76% accuracy on their benchmarks (they call it a "wall") in OCR tasks. that is, feeding it a picture of a document and asking it to extract the text.
They say some specialist models get better results on their benchmarks (Nanonets OCR-3 85.9%)
chelm 3 hours ago [-]
I linked your board already. You are right.
Do you know a benchmark that tries to measure the bussines accuracy.
Most benchmarks focus on the charackter level.
IDP Software typically uses metadata to map information that is either not readable or missing in the document, e.g. extracting the VAT and mapping the street, house number, cip and city.
I think there are many models and many providers. However, it's really difficult to measure the accuracy on a porcess not just on a character level.
I saw that the leaderboard is hosted by Nanonets. Totally fine for me. So you might be the expert about Nanonets: Let me know if you want to update your post on my site.
RugnirViking 2 hours ago [-]
it's not my site, I have nothing to do with nanonets. the information was taken from the article.
chelm 2 hours ago [-]
tl;dr: years ago, Tesseract was the go to tool to extract text. Nowadays, vLLMs can not only extract the text and the layout but also context and provide structured data or even interpret or map data across documents. Prices dropped significantly, while extraction, classification and modification capabilities increased.
The intelligent document processing (a funny marketing term on top of OCR) market moves from "Can software extract the text", which is normally measured by benchmarks, to can software autonomously run "a" specific company process.
the fallback is called human in the loop, hallucination (LSTM vs. vLLM), prompt engineering.
proof me wrong: the hardest challenge is no longer the OCR accuracy but the integration and issue handling in production. Probably "an agentic team can handle this" ^^
nullc 3 hours ago [-]
I mean this is for handwritten OCR.. do humans do better?
I've been using Qwen3.6 to OCR stuff, primary receipts and it frequently accurately reads stuff on mangled/faded/folded documents that I have a hard time with... including handwritten stuff (though that's not flawless).
chelm 3 hours ago [-]
ahahah, probably not. Looking at my own handwriting: Neither in writing nor in reading.
I find it interesting how the prompt changes the result.
If you let the model focus on the text, the open source got so good in the last year. That's remarkable. When you change to prompt to not only extract the text but also extract specific information, the pure text extraction result gets worse. For me, it worked to run two prompts on the same document to get both in a meaningful accruacy.
The benchmark site is here https://www.idp-leaderboard.org/
They say some specialist models get better results on their benchmarks (Nanonets OCR-3 85.9%)
Do you know a benchmark that tries to measure the bussines accuracy.
Most benchmarks focus on the charackter level.
IDP Software typically uses metadata to map information that is either not readable or missing in the document, e.g. extracting the VAT and mapping the street, house number, cip and city.
I think there are many models and many providers. However, it's really difficult to measure the accuracy on a porcess not just on a character level.
https://idp-software.com/vendors/nanonets/
I saw that the leaderboard is hosted by Nanonets. Totally fine for me. So you might be the expert about Nanonets: Let me know if you want to update your post on my site.
The intelligent document processing (a funny marketing term on top of OCR) market moves from "Can software extract the text", which is normally measured by benchmarks, to can software autonomously run "a" specific company process.
the fallback is called human in the loop, hallucination (LSTM vs. vLLM), prompt engineering.
proof me wrong: the hardest challenge is no longer the OCR accuracy but the integration and issue handling in production. Probably "an agentic team can handle this" ^^
I've been using Qwen3.6 to OCR stuff, primary receipts and it frequently accurately reads stuff on mangled/faded/folded documents that I have a hard time with... including handwritten stuff (though that's not flawless).
I find it interesting how the prompt changes the result.
If you let the model focus on the text, the open source got so good in the last year. That's remarkable. When you change to prompt to not only extract the text but also extract specific information, the pure text extraction result gets worse. For me, it worked to run two prompts on the same document to get both in a meaningful accruacy.