Pick the statement that best describes a scoring rubric in LLM evaluation.

A **scoring rubric** is a document that tells the judge exactly what each score level means. Without it, a '4 out of 5' is meaningless because different judges interpret the scale differently. A well-designed rubric has three parts. First, it names the quality dimensions being evaluated: accuracy, helpfulness, completeness, tone. Second, it defines what each score level means for each dimension. For example: '5 = fully correct, complete, and well-structured. 3 = mostly correct but missing important details. 1 = factually wrong or irrelevant.' Third, it includes anchor examples: concrete model outputs that illustrate what a 1, 3, and 5 actually look like. The rubric matters because it is what turns a subjective 'how good is this?' into a structured task. Without it, one judge might focus on accuracy while another focuses on tone, and both assign the same numeric score meaning different things. With a rubric, both judges evaluate the same dimensions using the same criteria. This applies equally to human judges and LLM judges. When you use an LLM as a judge, the rubric is embedded in the eval prompt template. The judge reads the criteria and anchor examples before scoring, which grounds its judgment.

A **scoring rubric** defines what each score level (e.g., 1 through 5) means with explicit criteria and ideally anchor examples. It turns a vague 'rate quality' task into a structured judgment that different judges can apply consistently. Without a rubric, two judges can both give a '4' but mean completely different things. One might mean 'accurate but incomplete.' The other might mean 'complete but has a tone issue.' The number is the same, but the signal is different. A rubric eliminates this ambiguity by specifying what each number means on each dimension. Anchor examples are the highest-leverage component. Instead of just describing a score level in abstract terms, you show the judge a concrete output that deserves that score. Anchors reduce interpretation variance because the judge has a reference point to compare against. In LLM-as-judge pipelines, the rubric is embedded in the eval prompt template. The judge reads the criteria and anchors before evaluating. Research shows that rubrics with anchor examples produce higher inter-rater agreement than rubrics with criteria descriptions alone. The G-Eval approach goes further by adding chain-of-thought reasoning: the judge evaluates each criterion explicitly before assigning a final score. The practical discipline: never deploy an LLM judge without a rubric. A judge without a rubric is making up its own criteria, and those criteria shift with prompt context, model version, and input distribution.