<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>LLM-as-Judge on DATATWEETS</title><link>https://datatweets.com/courses/llm-evaluation/llm-as-judge/</link><description>Recent content in LLM-as-Judge on DATATWEETS</description><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2026 Datatweets</copyright><lastBuildDate>Tue, 07 Jul 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://datatweets.com/courses/llm-evaluation/llm-as-judge/index.xml" rel="self" type="application/rss+xml"/><item><title>Lesson 1 - Why and When to Use an LLM Judge</title><link>https://datatweets.com/courses/llm-evaluation/llm-as-judge/lesson-1-why-and-when-to-use-an-llm-judge/</link><pubDate>Tue, 07 Jul 2026 09:00:00 +0200</pubDate><guid>https://datatweets.com/courses/llm-evaluation/llm-as-judge/lesson-1-why-and-when-to-use-an-llm-judge/</guid><description>Deterministic metrics from Module 3 cannot tell a correct paraphrase from a wrong answer &amp;ndash; a fluent answer that flips the meaning can still out-score a right one on F1. This lesson introduces the LLM-as-judge pattern: prompt a capable model with the question, the answer, and a reference, and ask for a correct/incorrect verdict with a reason. You build a live reference-based judge with claude-haiku-4-5 on four Docent items where F1 fails, and see the judge grade a correct paraphrase (F1 0.15) as correct and a fluent wrong answer (F1 0.80) as incorrect. It also covers the three judging modes the module explores, the judge&amp;rsquo;s real risks, and when a deterministic check is the better, cheaper tool.</description></item><item><title>Lesson 2 - Rubric &amp; Direct Scoring</title><link>https://datatweets.com/courses/llm-evaluation/llm-as-judge/lesson-2-rubric-and-direct-scoring/</link><pubDate>Tue, 07 Jul 2026 09:00:00 +0200</pubDate><guid>https://datatweets.com/courses/llm-evaluation/llm-as-judge/lesson-2-rubric-and-direct-scoring/</guid><description>A bare &amp;lsquo;rate this answer 1-5&amp;rsquo; drifts run to run and tells you nothing about what was wrong. This lesson builds a rubric that defines each criterion — Correctness, Groundedness, Helpfulness — and what every score level means, so a judge maps an answer to an explicit rung instead of guessing a number. You&amp;rsquo;ll write judge_answer() calling claude-haiku-4-5 for a structured JSON verdict with the rationale before the scores, validate and parse that JSON, aggregate per criterion, and run it live on four Docent answers — a strong one, a vague one, a hallucinated one, a wrong-fact one — watching groundedness collapse on the invented answer while correctness stays higher elsewhere.</description></item><item><title>Lesson 3 - Pairwise Comparison &amp; Preference</title><link>https://datatweets.com/courses/llm-evaluation/llm-as-judge/lesson-3-pairwise-comparison-and-preference/</link><pubDate>Tue, 07 Jul 2026 09:00:00 +0200</pubDate><guid>https://datatweets.com/courses/llm-evaluation/llm-as-judge/lesson-3-pairwise-comparison-and-preference/</guid><description>Instead of scoring one answer in isolation, pairwise judging asks the model which of two answers is better and aggregates the verdicts into a win-rate &amp;ndash; the backbone of preference evaluation and leaderboards. This lesson builds a real judge_pairwise on claude-haiku-4-5, runs a good Docent variant against a vague one to get a 0.75 win-rate, then exposes the headline pitfall: on near-equal answers the judge flips its verdict one to two times out of four just by swapping the order, and one pair flips on every single run. You fix it by running both orders and counting only order-consistent verdicts, and meet the other biases &amp;ndash; verbosity, ties, and broken transitivity.</description></item><item><title>Lesson 4 - Calibrating &amp; Trusting the Judge</title><link>https://datatweets.com/courses/llm-evaluation/llm-as-judge/lesson-4-calibrating-and-trusting-the-judge/</link><pubDate>Tue, 07 Jul 2026 09:00:00 +0200</pubDate><guid>https://datatweets.com/courses/llm-evaluation/llm-as-judge/lesson-4-calibrating-and-trusting-the-judge/</guid><description>A judge is a model, and a model can be confidently, systematically wrong. This lesson gives you the discipline that makes an LLM judge usable: calibrate it against human labels. You&amp;rsquo;ll meet the biases that break naive judges — position, verbosity, self-preference, leniency and severity, prompt sensitivity — then treat the judge as a classifier and score it against a ten-item human gold set for Docent. You&amp;rsquo;ll compute raw agreement and Cohen&amp;rsquo;s kappa for a naive judge (0.40 agreement, kappa minus 0.07 — worse than chance) and a grounded judge (1.00 agreement, kappa 1.00), watch the fix move every item onto the diagonal, and run a verbosity-bias probe.</description></item><item><title>Lesson 5 - Guided Project: A Calibrated Judge for Docent</title><link>https://datatweets.com/courses/llm-evaluation/llm-as-judge/lesson-5-guided-project-calibrated-judge/</link><pubDate>Tue, 07 Jul 2026 09:00:00 +0200</pubDate><guid>https://datatweets.com/courses/llm-evaluation/llm-as-judge/lesson-5-guided-project-calibrated-judge/</guid><description>The capstone for Module 4. You assemble the module into one runnable artifact: a judge_answer function on claude-haiku-4-5 that returns validated JSON with reasoning before a correct/incorrect verdict, run live over Docent&amp;rsquo;s ten-item golden set, then calibrated against hand-authored human gold labels on a mixed set of right and wrong answers. You compute judge-human agreement and Cohen&amp;rsquo;s kappa, set a trust threshold, inspect a real disagreement, and finally report Docent&amp;rsquo;s judged quality score with its calibration caveat attached &amp;ndash; never a judge score without the number that says how far to trust it.</description></item></channel></rss>