A graph-theoretic approach to building reliable LLM judges for retrieval
The article discusses the challenges of evaluating retrieval systems without ground-truth labels, particularly in sensitive domains like healthcare and legal. It proposes using large language models (LLMs) as judges to assess relevance based on task-specific rubrics instead of traditional labeling methods. This approach aims to overcome the limitations of existing metrics that rely on pre-existing relevance judgments.
- ▪Evaluating retrieval systems often requires ground-truth labels, which can be difficult to obtain in sensitive domains.
- ▪Embedding models may not accurately reflect task-specific relevance, leading to potential misclassifications.
- ▪Using LLMs as judges allows for qualitative assessments based on custom rubrics, reducing the need for extensive labeling efforts.
2 outlets in our directory ran this story, first to last over 15 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ Building Trustworthy LLM Judges — Withemissary
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,321 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Hacker News (AI / LLM) |
| Canonical URL | https://georgianailab.substack.com/p/evaluating-retrieval-without-ground |
| Publication time | Fri, 29 May 2026 14:31:11 +0000 |
| Retrieval time | 2026-05-29T14:45:01.332Z |
| Last seen | 2026-05-29T14:45:01.332Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | MjuJ4C5LsOOM · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Evaluating Retrieval Without Ground TruthA graph-theoretic approach to building reliable LLM judges for retrieval and rankingWilliam Barber and Kshitij JainMay 29, 202611ShareRecently, we have been spending a significant amount of time optimizing semantic retrieval pipelines across retrieval-augmented generation (RAG), threat detection, code search, legal search and recommendation systems. We keep hitting the same wall: a lack of ground-truth labels.In threat detection, raw data can be highly sensitive and often cannot leave the customer’s environment, making external labeling a non-starter. In healthcare and legal, labeling needs domain experts, and privacy rules narrow the pool of experts you are allowed to use.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (AI / LLM).