3 ms·

> The "best" models just made stuff up to meet the requirements. They lied in three ways: > The main difficulty of the is project lies in correctly identifying

> The "best" models just made stuff up to meet the requirements. They lied in three ways: > The main difficulty of the is project lies in correctly identifying page zones; wouldn't it be possible to properly find the zones during the OCR phase itself instead of rebuilding them afterwards? Anyone curious, try LLMWhisperer[1] for OCR. It doesn't use LLMs, so no hallucination side effects. It also preserves the layout of the input document for more context and clarity. [1] https://unstract.com/llmwhisperer/ https://unstract.com/llmwhisperer/ Examples of extracting complex layout: https://imgur.com/a/YQMkLpA https://imgur.com/a/YQMkLpA https://imgur.com/a/NlZOrtX https://imgur.com/a/NlZOrtX https://imgur.com/a/htIm6cf https://imgur.com/a/htIm6cf

bambax 2y ago
Looks interesting, but the cost is prohibitive for a hobby project. Also, it doesn't really solve my problem. Google Vision already returns the coordinates of each word (and even of each letter), so it's easy to know where the word was on the page, and even, if necessary, to rebuild the page with the words correctly placed -- that's fundamentally what I do with the mouseover on the interactive demo: https://divers.medusis.net/boislisle/pub https://divers.medusis.net/boislisle/pub (at the paragraph level). But my problem isn't to know where the words are (Google Vision provides that); it's to know what belongs to what, what is footnotes, what is main text, etc. This is what the post discusses. Just having the text following the same layout as in the original wouldn't help, because I'm not trying to reproduce the layout or the typesetting, I want to rebuild the content semantically, so as to do different "flows". That said, it got me thinking... there may be an opportunity to do a cheaper version of LLMwhisperer? ;-)
lethibo 2y ago
[dead]

bambax 2y ago

Looks interesting, but the cost is prohibitive for a hobby project. Also, it doesn't really solve my problem. Google Vision already returns the coordinates of each word (and even of each letter), so it's easy to know where the word was on the page, and even, if necessary, to rebuild the page with the words correctly placed -- that's fundamentally what I do with the mouseover on the interactive demo: https://divers.medusis.net/boislisle/pub https://divers.medusis.net/boislisle/pub (at the paragraph level). But my problem isn't to know where the words are (Google Vision provides that); it's to know what belongs to what, what is footnotes, what is main text, etc. This is what the post discusses. Just having the text following the same layout as in the original wouldn't help, because I'm not trying to reproduce the layout or the typesetting, I want to rebuild the content semantically, so as to do different "flows". That said, it got me thinking... there may be an opportunity to do a cheaper version of LLMwhisperer? ;-)

lethibo 2y ago

[dead]