Frontend
Every Edge Needs a Quote: Building a Quote-Grounded Knowledge Graph of Healthcare Software Adoption with Language-Model Agents
arXiv cs.IR0 views
arXiv:2610.32781v1 Announce Type: cross Abstract: Hospitals regularly buy software that clinicians and patients depend on. Because these purchases are costly, hard to reverse and can affect patient care, buyers look for evidence of which peer institutions already use a product and which systems it connects to. This evidence is public but scattered across vendor websites, press releases and third-party pages. Language-model agents can now collect it at low cost, but the correctness of the extracted claims is difficult to establish, and a wrongly listed customer can mislead buyers and misrepresent an organisation. We present a pipeline that builds a knowledge graph of customer and integration relations from the open web under one rule: every edge must be supported by a verbatim quote from its source page. Pages come from a deterministic crawl of each vendor's site and a budgeted ReAct agent that searches the rest of the web. A permissive extractor proposes relations with quotes, and a layered grounding stage decides which to keep, using a referent step that reads the whole page when a quote names only one side, deterministic checks, and a panel of five model calls voting on nine criteria. On 61 vendors, the pipeline reaches 0.94 precision and 0.71 recall against a page-level key covering the 6,428 candidate relations proposed by its extractor, whose verdicts were drafted by one model and re-checked with a second. Against the golden reference, the marketplace's own curated list, it scores lower, but 89% of the relations it keeps that the reference lacks are stated on a page. A confidence score built from the panel's votes keeps more correct relations than the fixed rule at the same precision, and reaches 0.90 precision at 0.90 recall. We also discuss how narrow, bounded model calls, string-matched evidence and voting address long-context degradation and run-to-run variance.
Source:https://arxiv.org/abs/2610.32781PreviousSystem One models Are Not Better RerankersNextDriving Video Retrieval for Complex Queries with Structured Grounding
Related posts

The Effort to Reach: Designing for Fitts’s Law
0dev.to UX
GitHub’s New Dependabot Verdict Can Lag Behind Your Next Commit
0dev.to GitHub

Document Review With Unsiloed and TypeSafe Jev
0dev.to Machine Learning
AmeriHealth Caritas Files 61-Worker WARN Notice in Orlando, Effective December 31, 2026
0dev.to Career
Remote SWE Jobs Paying Up to $220k (Nov 2)
0dev.to Career
What are your goals for the week? #203
0dev.to Career