It's shocking how much our industry fails to see past its own nose. Not a single example on that page is a Purchase Order, Invoice etc. Not a single example shown is relevant to industry at scale.
Mistral OCR
211–220 of 450 posts
Re: Mistral OCR
#212Earlier quoted context omitted.
hence my comment about privacy and need for legislation :) It isn't the tech that's the problem but the people that will abuse it.
While those are concerns, my point was that having everything on the internet navigated to, digested and explained to me sounds unpleasant and overall a drain on my ability to think and reason for myself. It is specifically how you describe using the tech that provokes a feeling of revulsion to me.
Re: Mistral OCR
#213Its funny how Gemini consistently beats googles dedicated document API.
Re: Mistral OCR
#214We're approaching the point where OCR becomes "solved" — very exciting! Any legacy vendors providing pure OCR are going to get steamrolled by these VLMs. However IMO, there's still a large gap for businesses in going from raw OCR outputs —> document processing deployed in prod for mission-critical use cases. LLMs and VLMs aren't magic, and anyone who goes in expecting 100% automation is in for a surprise. You still n…
One problem I’ve encountered at my small startup in evaluating OCR technologies is precisely convincing stakeholders that the “human-in-the-loop” part is both unavoidable, and ultimately beneficial. PMs want to hear that an OCR solution will be fully automated out-of-the-box. My gut says that anything offering that is snake-oil, and I try to convey that the OCR solution they want is possible, but if you are unwilling…
But that doesn't mean you have to abandon the effort. You can still definitely achieve production-grade accuracy! It just requires having the right tooling in place, which reduces the upfront tuning cost. We typically see folks get there on the order of days or 1-2 weeks (it doesn't necessarily need to take months).
Re: Mistral OCR
#215It's shocking how much our industry fails to see past its own nose. Not a single example on that page is a Purchase Order, Invoice etc. Not a single example shown is relevant to industry at scale.
Re: Mistral OCR
#216It's shocking how much our industry fails to see past its own nose. Not a single example on that page is a Purchase Order, Invoice etc. Not a single example shown is relevant to industry at scale.
Mistral is Europe based where invoices are more or less sent digitally in like 95% of all the cases anyway. Some are even digital invoices, which will at some point in the eu be mandatory. For orders there are proposals for that, too. And basically invoice data extraction is a different beast.
Re: Mistral OCR
#217I tried with both PDFs and PNGs in Le Chat and the results were the worst I've ever seen when compared to any other model (Claude, ChatGPT, Gemini). So bad that I think I need to enable the OCR function somehow, but couldn't find it.
Re: Mistral OCR
#218They say: "releasing the API mistral-ocr-latest at 1000 pages / $" I had to reread that a few times. I assume this means 1000pg/$1 but I'm still not sure about it.
Great example of how information is sometimes compartmentalized arbitrarily in the brain: I imagine you have never been confused by sentences such as “I’m running at 10 km/h”.
Re: Mistral OCR
#219It's shocking how much our industry fails to see past its own nose. Not a single example on that page is a Purchase Order, Invoice etc. Not a single example shown is relevant to industry at scale.
Re: Mistral OCR
#220Earlier quoted context omitted.
Now? OK, you need to screencap and upload to LLM, but that's well established tech by now. (Where by "well established", I mean at least 9 months old ;) Same goes for "navigating HTTP sites via LLM prompts". Most LLMs have web search integration, and the "Deep Research" variants do more complex navigation. Video chat is there partially, as well. It doesn't really pay much attention to gestures & expressions, but I'd…
Yeah, all these things are possible today, but getting them well polished and integrated is another story. Imagine all this being supported by "HTML6" lol. When apple gets around to making this part of safari, then we know it's ready.
But kidding aside - I'm not sure people want this being supported by web standards. We could be a huge step closer to that future had we decided to actually take RDF/Dublin Core/Microdata seriously. (LLMs perform a lot better with well-annotated data)
The unanimous verdict across web publishers was "looks like a lot of work, let's not". That is, ultimately, why we need to jump through all the OCR hoops. Not only did the world not annotate the data, it then proceeded to remove as many traces of machine readability as possible.
So, the likely gating factor is probably not Apple & Safari & "HTML6" (shudder!)
If I venture my best bet what's preventing polished integration: It's really hard to do via foundational models only, and the number of people who want to have deep & well-informed conversations via a polished app enough that they're willing to pay for an app that does that is low enough that it's not the hot VC space. (Yet?)
Crystal ball: Some OSS project will probably get within spitting distance of something really useful, but also probably flub the UX. Somebody else will take up these ideas while it's hot and polish it in a startup. So, 18-36 months for an integrated experience from here?