<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DocETL: Agentic Query Rewriting and Evaluation for Complex Document Processing · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2410.12189/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2410.12189/feed.xml" rel="self" type="application/rss+xml" /><item><title>DocETL: Agentic Query Rewriting and Evaluation for Complex Document Processing — mentioned by anishathalye</title><link>https://news.ycombinator.com/item?id=45250441</link><guid isPermaLink="false">urn:hackerpapers:mention:2410.12189:45250441</guid><pubDate>Mon, 15 Sep 2025 14:55:29 GMT</pubDate><description>&lt;p&gt;That was a small self-contained example that fit above the fold in the README (and fwiw even last year’s models like GPT-4o give the right output there). That `sort` is based on pairwise comparisons, which is one of the best ways you can do it in terms of accuracy (Qin et al., 2023: https://arxiv.org/abs/2306.17563). I think there are many real use cases where you might want a semantic sort / semantic data processing in general, when there isn’t a deterministic way to do the task and there is not necessarily a single right answer, and some amount of error (due to LLMs being imperfect) is…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2410.12189/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DB</category></item></channel></rss>
