By far the best one I've come across is Microsoft Azure Document Intelligence with the Layout Model[0].
It's really, really good at tables.
You have to use the Layout Model and not just the base Document Intelligence.
A bit pricey, but if you're processing content one time and it's high value (my use case as clinical trial protocol documents and the trial will run anywhere from 6-24 months), then it's worth it, IMO.
There's reliable, and there's reliable. For example [1] is a conversation where I ask ChatGPT 4o questions about a seven-page tabular PDF from [2] which contains a list of election polling stations.
The results are simultaneously impressive and unimpressive. The document contains some repeated addresses, and the LLM correctly identifies all 11 of them... then says it found ten.
It gracefully deals with the PDF table, and converts the all-caps input data into Title Case.
The table is split across multiple pages, and the title row repeats each time. It deals with that easily.
It correctly finds all five schools mentioned.
When asked to extract an address that isn't in the document it correctly refuses, instead of hallucinating an answer.
When asked to count churches, "Bunyan Baptist Church" gets missed out. Of two church halls, only one gets counted.
The "Friends Meeting House" also doesn't get counted, but arguably that's not a church even if it is a place of worship.
Longmeadow Evangelical Church has one address, three rows and two polling station numbers. When asked how many polling stations are in the table, the LLM counts that as two. A reasonable person might have expected one, two, three, or a warning. If I was writing an invoice parser, I would want this to be very predictable.
So, it's a mixed bag. I've certainly seen worse attempts at parsing a PDF.
You can try to ask it to list all churches and assign them incremental number starting with 1. then print the last number. It's a variation of counting 'r' in 'raspberry' which works better than simple direct question.
> There's reliable, and there's reliable. For example [1] is a conversation where I ask ChatGPT 4o questions about a seven-page tabular PDF from [2] which contains a list of election polling stations.
From your description, it does perfectly at the task asked about upthread (extraction) and has mixed results on other, question-answering, tasks, that weren't the subject.
> From your description, it does perfectly at the task asked about upthread (extraction) and has mixed results on other, question-answering, tasks, that weren't the subject.
Do I understand correctly that nearly all issues were related to counting (i.e. numerical operations)? that makes it still impressive because you can do that client-side with the structured data
As someone that spent quite a bit of time with table-transformers, I would definitely not recommend it. It was one of the first libraries we added for parsing tables into our chunking library [1] and the results were very underwhelming. This was a while back and at this point, it's just so much easier to use an LLM end to end for parsing docs (Gemini Flash can parse 20k pages per dollar) and I'm wary of any approach that stitches together different models.
I would like to through our project in the ring. We use ColQwen2 over a ColPali implementation. Basically, search & extract pipeline: https://docs.colivara.com/guide/markdown
Ah so like NIM is a set of microservices on top of various models, and this is another set of microservices using NIM microservices to do large scale OCR?
and that too integrated with prometheus, 160GB VRAM requirement and so on?
Looks like this is targeted for enterprises or maybe governments etc trying to digitalize at scale.
How is this different than elasticsearch and solr? That’s not any kind of challenging question… I really don’t know that much about these different tools and I just want to know what this one is about.
Also: I noticed that it mentioned images… does it do any kind of OCR or summary of them?
It is a method of extracting structured data from messy documents meant for human consumption that can then be indexed by tools like Elasticsearch and solr.
I have hard time to understand what they mean by "early access micro services"...?
Does it mean that it is yet another wrapper library to call they proprietary cloud api?
Or that when you have the specific access right, you can retrieve a proprietary docker image with secret proprietary binary stuffs inside that will be the server used by the library available in GitHub?
The latter. NIMs is Nvidia's umbrella branding for proprietary containerized AI models, which is being pushed hard by Jensen. They build models and containers, then push them to ngc.nvidia.com. They then provide reference architectures which rely on them. In this case the images are in an invite only org, so to use the helm chart you have to sign up, request access, then use an API key to pull the image.
lol, while checking which OCR is using (PaddleOCR) I found a line with the text: "TODO(Devin)" and was pretty excited thinking they were already using Devin AI...
"Devin Robison" is the author of the package!! Funny, guess it will be similar with the name Alexa
Why even buy them at this point... just rent neocloud for $1-2... even at $2/hr, that's over a year of rental for $25k... by then you'd have made your money off the implementation.
Even at $3/hour (which is above the current market rate), that's roughly a year.
I genuinely appreciate your perspective, but as a smaller, lesser-known provider, I’d like to understand your concerns better.
Are you worried that I might misuse your data and compromise my entire business, by selling it to the highest bidder? Do you feel uncertain about the security of my systems? Or is it a belief that owning and managing the hardware yourself gives you greater control over security?
What kind of validation or reassurance would help address these concerns?
If it was a GPT wrapper, it wouldn't require an A100/H100 GPU; the container has a model wrapper, sure, but also it has the wrapped, standalone model, as well; its not calling OpenAI's model.
It's really, really good at tables.
You have to use the Layout Model and not just the base Document Intelligence.
A bit pricey, but if you're processing content one time and it's high value (my use case as clinical trial protocol documents and the trial will run anywhere from 6-24 months), then it's worth it, IMO.
[0] https://learn.microsoft.com/en-us/azure/ai-services/document...
In my experience, the latest Gemini is best at vision and OCR
There's reliable, and there's reliable. For example [1] is a conversation where I ask ChatGPT 4o questions about a seven-page tabular PDF from [2] which contains a list of election polling stations.
The results are simultaneously impressive and unimpressive. The document contains some repeated addresses, and the LLM correctly identifies all 11 of them... then says it found ten.
It gracefully deals with the PDF table, and converts the all-caps input data into Title Case.
The table is split across multiple pages, and the title row repeats each time. It deals with that easily.
It correctly finds all five schools mentioned.
When asked to extract an address that isn't in the document it correctly refuses, instead of hallucinating an answer.
When asked to count churches, "Bunyan Baptist Church" gets missed out. Of two church halls, only one gets counted.
The "Friends Meeting House" also doesn't get counted, but arguably that's not a church even if it is a place of worship.
Longmeadow Evangelical Church has one address, three rows and two polling station numbers. When asked how many polling stations are in the table, the LLM counts that as two. A reasonable person might have expected one, two, three, or a warning. If I was writing an invoice parser, I would want this to be very predictable.
So, it's a mixed bag. I've certainly seen worse attempts at parsing a PDF.
[1] https://chatgpt.com/share/67812ad9-f2bc-8011-96be-faea40e48d... [2] https://www.stevenage.gov.uk/documents/elections/2024-pcc-el...
From your description, it does perfectly at the task asked about upthread (extraction) and has mixed results on other, question-answering, tasks, that weren't the subject.
¯\_(ツ)_/¯
Which do you think was which?
This is much lighter weight and more reliable than vllm
[1] https://github.com/Filimoa/open-parse/
and that too integrated with prometheus, 160GB VRAM requirement and so on?
Looks like this is targeted for enterprises or maybe governments etc trying to digitalize at scale.
Also: I noticed that it mentioned images… does it do any kind of OCR or summary of them?
https://lambdalabs.com/nvidia-gh200
Does it mean that it is yet another wrapper library to call they proprietary cloud api?
Or that when you have the specific access right, you can retrieve a proprietary docker image with secret proprietary binary stuffs inside that will be the server used by the library available in GitHub?
You can imagine how fun it is to debug.
The open question is whether to use rule-based parsing using simpler software or model-based parsing using this software.
"Devin Robison" is the author of the package!! Funny, guess it will be similar with the name Alexa
I genuinely appreciate your perspective, but as a smaller, lesser-known provider, I’d like to understand your concerns better.
Are you worried that I might misuse your data and compromise my entire business, by selling it to the highest bidder? Do you feel uncertain about the security of my systems? Or is it a belief that owning and managing the hardware yourself gives you greater control over security?
What kind of validation or reassurance would help address these concerns?