LLM-as-a-Judge Field Guide
The Mitigation Toolkit, Ranked by How Solved It Actually Is9. The Honest Interlude: I Tried to Find You Something Novel10. The War Room Reference TableConclusion: The Fundamentals Are Settled.
- ▪The Mitigation Toolkit, Ranked by How Solved It Actually Is9.
- ▪The Honest Interlude: I Tried to Find You Something Novel10.
- ▪The War Room Reference TableConclusion: The Fundamentals Are Settled.
Hacker News (AI / LLM) files mainly under ai. We currently carry 2,762 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 | Karthika Raghavan |
| Canonical URL | https://kraghavan.ca/llm-infrastructure/evaluation/2026/07/25/llm-as-a-judge-field-guide.html |
| Publication time | Sun, 26 Jul 2026 05:17:30 +0000 |
| Retrieval time | 2026-07-26T05:32:48.004Z |
| Last seen | 2026-07-26T05:32:48.004Z |
| 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 | xDJnCLG_4dTt |
| 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
On this page 1. What Is LLM-as-a-Judge?2. Why It Had to Exist3. The Papers That Built the Field4. Where It’s Actually Used Today5. The Bias Zoo6. Where Judges Fall Off a Cliff7. When Judges Get Attacked on Purpose8. The Mitigation Toolkit, Ranked by How Solved It Actually Is9. The Honest Interlude: I Tried to Find You Something Novel10. Where the Frontier Actually Is11. The War Room Reference TableConclusion: The Fundamentals Are Settled. The Frontier Is Not.References Let me be honest about how this post happened, because it’s a better story than the post itself. I wanted to learn LLM-as-a-judge properly — not “yeah, you use an LLM to grade another LLM’s output” properly, but actually understand where it came from, where it breaks, and what people smarter than me are doing about it.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Karthika Raghavan.
Discussion
0 commentsMore from Karthika Raghavan
