Загрузка видео...

Не удалось загрузить видео

На главную

Astra is awesome, but if you're using it specifically to parse and extract a massive volume of documents, you will break the bank (10c+ per page on parsing and extraction!) We've added a native LlamaParse connector to ChatGPT that gives the model access to high-quality document OCR and extraction...

10,796 просмотров • 3 дней назад •via X (Twitter)

Комментарии: 10

Фото профиля Imaan Sultan 🇵🇰🇸🇦
Imaan Sultan 🇵🇰🇸🇦3 дней назад

this is sickkkk

Фото профиля Kevihaiceth 💹🧲
Kevihaiceth 💹🧲3 дней назад

Gonna try this with my messy PDFs

Фото профиля Victor Bolshakov
Victor Bolshakov3 дней назад

Extraction gets the values in. We measured what happens after. With the tables on disk and a shell, conditions missing the definitions did not improve, and answers matching a superseded rule went from 16.2% to 29.4%. Good parsing without definitions reads better than it is.

Фото профиля Benny
Benny3 дней назад

This is the real routing problem: frontier models are great at reasoning, terrible as a default for specialized high-volume jobs. Buyers who pick “one model for everything” get surprised by the bill. Route the specialist work to specialist infra.

Фото профиля RIDER SKETCH
RIDER SKETCH3 дней назад

this is probably the right way to use AI. let Astra handle the reasoning. let LlamaParse do the document grunt work. using an expensive frontier model to read every page is a very expensive habit.

Фото профиля John Rood
John Rood3 дней назад

the next unlock is routing per page, not per document. let the cheap parser own clean pages and send only low-confidence spans plus surrounding evidence to Astra. frontier models should be the exception path, not a tax on every page.

Фото профиля KURAOpenclaw
KURAOpenclaw3 дней назад

10c+ per page is insane for massive document parsing; LlamaParse sounds like a necessary fix to make this actually scalable without emptying your wallet.

Фото профиля Voxlessa
Voxlessa2 дней назад

Can the extracted result keep page references back to the original? With a messy scan, being able to check one suspicious number quickly is very useful.

Фото профиля Naree Suwannarak
Naree Suwannarak2 дней назад

".

Фото профиля Niel Pal
Niel Pal3 дней назад

connector is clutch

Похожие видео

Introducing ExtractBench, the most comprehensive benchmark for information extraction from complex enterprise documents. The latest models are pushing the frontier of coding and knowledge work, but surprisingly they still struggle on complex doc extraction tasks in production. A well-tuned extractor must parse multi-page filings without dropping rows, emit exact spatial citations for auditability, and handle messy scans. Also they must do all of this at a viable per-page cost so that you can scale this to millions of docs in production (you can’t be paying upwards of $1 in tokens per page!) Existing extraction benchmarks fall short: they are not large/diverse enough in document domain (finance, energy, gov, auto), elements (long records, scans, grounding), and schemas. So our applied research team built ExtractBench. We evaluated 14 systems: frontier VLMs, coding agents, and specialized extraction APIs, against 370 enterprise documents: 4,869 pages, 67 document types. Our biggest finding 🧪: Short documents mask critical system flaws. On files past 50 pages, commercial VLMs collapse below 35% recall due to silent list truncation. They hold high precision, but lose output attention and drop most of the table rows. ExtractBench evaluates value accuracy, long-record completeness, spatial grounding, and per-page cost with zero LLM judges. It is 100% deterministic and reproducible. In tandem with ExtractBench, we’re also introducing 𝗔𝗴𝗲𝗻𝘁𝗶𝗰 𝗣𝗹𝘂𝘀, a new Extract tier in LlamaParse that debuts at #1 on the leaderboard: 95.6% value accuracy, at less than a third the cost of the closest peer. Explore the findings, download the dataset, or run the harness: Blog: GitHub: HuggingFace: We will be actively evolving both our extraction benchmark as well as our extraction harness over time. If you check out either ExtractBench or LlamaParse, let us know your feedback!

Jerry Liu

75,415 просмотров • 1 месяц назад

The latest RAG trend for the current agent harnesses (Codex, Cowork) is to do two passes of document processing to solve a knowledge work task over a data room of documents: 1️⃣ A fast and light pass, oftentimes using a free/OSS doc parsing tool. This can be cheaply run across 10-100-1k’s of files, and enables the agent to then do retrieval (e.g. grep, semantic) to find relevant subsets of context. 2️⃣ A “just-in-time” VLM-based pass. Once the agent finds the relevant pages of context, it will screenshot the documents can call its own VLM (or write code) to dissect the pages. The issue with only using VLM-based OCR tools over massive ad-hoc customer file dumps is that it’s slow and expensive. Doing JIT VLM OCR allows the agent to filter through the data cheaply, but still preserve accuracy for the context that’s needed for the task. The agent harnesses do two-pass document processing by default using off the shelf-tools: pdf2text as the first pass, and using itself (Opus 5) as the second pass. See the below video where Cowork runs over a bunch of PDFs to answer a question about a benchmark graph in the Kimi k3 paper. The main issues here with the “out of the box” doc processing these agents offer are: * Opus 5 is not the best VLM for OCR. It is also way too expensive at scale and lacks grounding * The OSS tools like pypdf, pdf2text, may not be versatile enough as the first pass. * The agent will write a lot of throwaway code to rewrite things an OCR tool would’ve provided out of the box, like chart processing, bounding boxes, confidence scores, leading to increased cost and speed. We have all the tools within LlamaIndex 🦙 to help any agent do two-pass document processing with higher accuracy and lower cost. 1️⃣ We have liteparse for the first pass - a free/OSS parser written in Rust that’s faster/more accurate than other OSS parsers, and supports 50+ document types 2️⃣ We have LlamaParse for the second pass - an agentic document engine that uses VLMs+harnesses to achieve SOTA in accuracy and cost across various doc parsing and extraction tasks. It can be called from any agent harness as an MCP or skill. It takes in page numbers as input, so that the agent can choose to run LlamaParse over a subset of the doc instead of the full doc as a “zoom-in” pass. Come check it out! LiteParse: LlamaParse: All the relevant docs, including MCP, are here:

Jerry Liu

22,763 просмотров • 20 дней назад