正在加载视频...

视频加载失败

Announcing: Agentic Document Extraction! PDF files represent information visually - via layout, charts, graphs, etc. - and are more than just text. Unlike traditional OCR and most PDF-to-text approaches, which focus on extracting the text, an agentic approach lets us break a document down into components and reason about...

689,571 次观看 • 1 年前 •via X (Twitter)

11 条评论

Arnav Jaitly 的头像
Arnav Jaitly1 年前

This is such a pain point for a lot of companies. Agentic information extraction will be such a productivity and efficiency boost

PDF GPT 的头像
PDF GPT2 年前

This is my favorite AI tool for reviewing reports. Just upload a report, ask for a summary, and get one in seconds. It's like ChatGPT, but built for documents. Try it for free.

Andrei Hasna 的头像
Andrei Hasna1 年前

Well done and well needed.

Vasilis K. 的头像
Vasilis K.1 年前

@JackPNicholls

The AI Agent Architect 的头像
The AI Agent Architect1 年前

Great use case. Using an agentic approach to this is kinda like getting the LLM to add metadata to what it finds in the PDF. So many thing you could do with that. If you want to see the opposite side of that coin - the creation of a structured Word document by an agent from only two simple commands, there will be a video demo showing this in my next article tomorrow.

🔮 的头像
🔮1 年前

Love what you’re doing! For what it’s worth the URL in your video is wrong and hits a 404

Mr Rio 的头像
Mr Rio1 年前

this is what I need

RyanRejoice 的头像
RyanRejoice1 年前

This is incredible and a game changer for handling and analyzing pdf data.

Clara Data 的头像
Clara Data1 年前

Innovative spin on PDFs! Looking promising for future efficiency!

Huxley MindOS 的头像
Huxley MindOS1 年前

Mastering the PDF mystery: deciphering both scroll & scribe! Sounds innovative. Looking forward to the details.

Javier Modified 的头像
Javier Modified1 年前

Agentic Document Extraction? Finally, AI can stop pretending it understands charts. This is how you handle a PDF! 🚀

相关视频

Build better RAG by letting a team of agents extract and connect your reference materials into a knowledge graph. Our new short course, “Agentic Knowledge Graph Construction,” taught by Neo4j Innovation Lead Andreas Kollegger, shows you how. Knowledge graphs are an important way to store information accurately but they are a lot of work to build manually. In this course you’ll learn how to build a team of agents that turn data– in this case product reviews and invoices from suppliers–into structured graphs of entities and relationships for RAG. Learn how agents can automatically handle the time-consuming work of building graphs — extracting entities and relationships (e.g., Product "contains" Assembly, Part "supplied_by" Supplier, Customer review "mentions" Product), deduplicating them, fact-checking them, and committing them to a graph database — so your retrieval system can find right information to generate accurate output. For example, you can use agents to help trace customer complaints directly to specific suppliers, manufacturing processes, and product hierarchies, thus turning fragmented information into queryable business intelligence. Skills you’ll gain: - Build, store, and access knowledge graphs using the Neo4j graph database - Build multi-agent systems using Google’s Agent Development Kit (ADK) - Set up a loop of agentic workflows to propose and refine a graph schema through fact-checking - Connect agent-generated graphs of unstructured and structured data into a unified knowledge graph This course gets into the practicum of why knowledge graphs give more accurate information retrieval than vector search alone, especially for high-stakes applications where precision matters more than fuzzy similarity matching. Sign up here:

Andrew Ng

168,153 次观看 • 1 年前

Traditional data pipelines don't work for RAG applications. There are 3 issues with them: ​ 1. Traditional data engineering solutions are optimized to handle structured data. RAG applications rely primarily on unstructured data. ​ 2. The connector ecosystem to load data from unstructured data sources is very immature. ​ 3. Traditional solutions do not offer any way to transform unstructured data into an optimized vector search index. ​ The goal of a RAG Pipeline is to solve these problems. ​ The number one objective is to create a reliable vector search index using factual knowledge and relevant context. This sounds easy, but it's one of the biggest challenges we face when building RAG applications. ​ At a high level, there are four different stages in the architecture of a RAG pipeline: ​ 1. Ingestion: Here is where the pipeline loads the information from the data source. ​ 2. Extraction: Where the pipeline processes the input data and decides how to retrieve the text contained inside them. ​ 3. Transform: Where the pipeline chunks the data and generates document embeddings. ​ 4. Load: Where the pipeline creates a search index in a vector database and loads the document embeddings. ​ There are different rabbit holes at each one of these stages. Here are three of them: ​ 1. Ingesting data once is simple. The hard part is refreshing the vector database whenever the original data source changes. ​ 2. Extracting the content of a plain text document is simple. The hard part is to extract content from complex documents containing tables, images, or cross-references. ​ 3. A simple continual chunking strategy with an overlap is simple. The hard part is to find the optimal strategy for your specific knowledge base and the way you are planning to query it. ​ In the attached video, I'll show you how you can build an enterprise-grade RAG Pipeline that solves every one of the above problems. ​ I'll use Vectorize. They partnered with me on this post. You can use them to build RAG pipelines optimized for accurate context retrieval. ​ ​ If you have a few documents lying around, set up a free account and give it a try.

Santiago

40,627 次观看 • 1 年前