Jerry Liu's banner
Jerry Liu's profile picture

Jerry Liu

@jerryjliu0 • 85,807 subscribers

Parsing the world's hardest PDFs @llama_index. cofounder/CEO LlamaParse: https://t.co/XYZmx5TFz8 Enterprise: https://t.co/Ht5jwxSrQB

Shorts

Parsing PDFs at scale with LLMs is cost prohibitive. Newer models (e.g. gemini 3) are good at reading pdfs, but you burn unnecessary vision tokens even when the page is text heavy. We’ve built in a “cost-optimizer” within LlamaParse that will dynamically route pages to fast/cheap parsing depending on its complexity. Complex pages (e.g. those with tables/charts/diagrams) will still get routed to our VLM-enabled modes. This will let you save anywhere from 50-90% of parsing costs, at much higher accuracy compared to the comparable mode of feeding screenshots into VLMs. Check it out!

Parsing PDFs at scale with LLMs is cost prohibitive. Newer models (e.g. gemini 3) are good at reading pdfs, but you burn unnecessary vision tokens even when the page is text heavy. We’ve built in a “cost-optimizer” within LlamaParse that will dynamically route pages to fast/cheap parsing depending on its complexity. Complex pages (e.g. those with tables/charts/diagrams) will still get routed to our VLM-enabled modes. This will let you save anywhere from 50-90% of parsing costs, at much higher accuracy compared to the comparable mode of feeding screenshots into VLMs. Check it out!

55,931 просмотров

The `rebel-large` model is awesome for relation extraction 🔗 Paired with CUDA, it’s blazing fast ⚡️. With LlamaIndex 🦙 🦙, we can now build a knowledge graph over any text data super quickly! 🕸️ Full Colab notebook showing how you can use it:

The `rebel-large` model is awesome for relation extraction 🔗 Paired with CUDA, it’s blazing fast ⚡️. With LlamaIndex 🦙 🦙, we can now build a knowledge graph over any text data super quickly! 🕸️ Full Colab notebook showing how you can use it:

181,829 просмотров

You might’ve known us as a “RAG framework” company - but we’ve been a best-in-class, agentic document OCR/workflow company for the past 1.5+ years! 📑🤖 We’re building the future of knowledge work over documents. Our website is awesome - check it out if you haven’t already 👇

You might’ve known us as a “RAG framework” company - but we’ve been a best-in-class, agentic document OCR/workflow company for the past 1.5+ years! 📑🤖 We’re building the future of knowledge work over documents. Our website is awesome - check it out if you haven’t already 👇

56,685 просмотров

Knowledge graphs are really cool 🧠 What’s even cooler is LLMs + knowledge graphs backed by a graph db (NebulaGraph) 🔥 This presents an entirely new stack for retrieval-augmented generation (separate from vector db + top-k)! Now possible with LlamaIndex 🦙 👇

Knowledge graphs are really cool 🧠 What’s even cooler is LLMs + knowledge graphs backed by a graph db (NebulaGraph) 🔥 This presents an entirely new stack for retrieval-augmented generation (separate from vector db + top-k)! Now possible with LlamaIndex 🦙 👇

113,738 просмотров

Super excited to feature TWO exciting AGI projects using GPT News 🔥⚡️ 🤖 llama_agi: Automatically execute tasks towards a goal! ⚙️ auto_llama: An internet agent to fulfill tasks. Link: GPT News makes AGI projects straightforward to build. 🧵

Super excited to feature TWO exciting AGI projects using GPT News 🔥⚡️ 🤖 llama_agi: Automatically execute tasks towards a goal! ⚙️ auto_llama: An internet agent to fulfill tasks. Link: GPT News makes AGI projects straightforward to build. 🧵

76,791 просмотров

Extracting structured outputs with LLMs is easy. But doing large-scale extraction with precise citations and bounding boxes back to the source documents is way harder. With our latest release in LlamaExtract, we extract citation bounding boxes along with every single key and value within a document. You can see this in the UI. Hover over any k:v pair and you’ll be able to see the corresponding highlights in the source doc. If you’re a human reviewing a million docs (resumes, IDs, invoices, claims, contracts), this will help you 5x your ability to verify values and make sure things are correct. Check out these new extraction upgrades in LlamaCloud:

Extracting structured outputs with LLMs is easy. But doing large-scale extraction with precise citations and bounding boxes back to the source documents is way harder. With our latest release in LlamaExtract, we extract citation bounding boxes along with every single key and value within a document. You can see this in the UI. Hover over any k:v pair and you’ll be able to see the corresponding highlights in the source doc. If you’re a human reviewing a million docs (resumes, IDs, invoices, claims, contracts), this will help you 5x your ability to verify values and make sure things are correct. Check out these new extraction upgrades in LlamaCloud:

23,044 просмотров

Automate ETL over Financial Data 📊 Most real-world financials are not “database-shaped”, and requires a ton of human effort to manipulate/copy an Excel sheet into structured formats for analysis. We recently launched LlamaSheets - a specialized AI agent that automatically structures your Excel spreadsheet into a 2D format for analysis. There are so many use cases for Excel, and accounting is a huge subcategory here. Check it out:

Automate ETL over Financial Data 📊 Most real-world financials are not “database-shaped”, and requires a ton of human effort to manipulate/copy an Excel sheet into structured formats for analysis. We recently launched LlamaSheets - a specialized AI agent that automatically structures your Excel spreadsheet into a 2D format for analysis. There are so many use cases for Excel, and accounting is a huge subcategory here. Check it out:

21,354 просмотров

Videos

jerryjliu0's profile picture

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,742 просмотров • 2 месяцев назад

jerryjliu0's profile picture

Parse PDFs at lightspeed (this video is at 1x) Absolute cinema

Jerry Liu

144,675 просмотров • 4 месяцев назад

jerryjliu0's profile picture

We’re open sourcing the first document OCR benchmark for the agentic era, ParseBench. Document parsing is the foundation of every AI agent that works with real-world files. ParseBench is a benchmark that measures parsing quality specifically for agent knowledge work: ✅ It optimizes for semantic correctness (instead of exact similarity) ✅ It has the most comprehensive distribution of real-world enterprise documents It contains ~2,000 human-verified enterprise document pages with 167,000+ test rules across five dimensions that matter most: tables, charts, content faithfulness, semantic formatting, and visual grounding. We benchmarked 14 known document parsers on ParseBench, from frontier/OSS VLMs to specialized parsers to LlamaParse. Here are some of our findings: 💡 Increasing compute budget yields diminishing returns - Gemini/gpt-5-mini/haiku gain 3-5 points from minimal to high thinking, at 4x the cost. 💡 Charts are the most polarizing dimension for evaluation. Most specialized parsers score below 6%, while some VLM-based parsers do a bit better. 💡 VLMs are great at visual understanding but terrible at layout extraction. GPT-5-mini/haiku score below 10% on our visual grounding task, all specialized parsers do much better. 💡 No method crushes all 5 dimensions at once, but LlamaParse achieves the highest overall score at 84.9%, and is the leader in 4 out of the 5 dimensions. This is by far the deepest technical work that we’ve published as a company. I would encourage you to start with our blog and explore our links to Hugging Face to GitHub. All the details are in our full 35-page (!!) ArXiv whitepaper. 🌐: Blog: 📄 Paper: 💻 Code: 📊 Dataset: 🎥 YouTube:

Jerry Liu

108,403 просмотров • 6 месяцев назад

jerryjliu0's profile picture

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

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