Skip to main content

OVERVIEW

An evaluator stores the configuration of a judge, including its prompt, model, and scoring structure. Saving an evaluator lets you apply the same judge across multiple evaluation runs without reconfiguring it each time. For instructions on saving and accessing evaluators from the UI, see Saved Evaluators. For the full schema reference, see Evaluator Schema.

COMMON RECIPE PATTERNS

GENERAL RESPONSE QUALITY JUDGE

Evaluates whether a model response is accurate, clear, and helpful. A good starting point for most fine-tuning workflows.
When to use: General-purpose evaluation for chatbots, assistants, and instruction-following tasks.

SAFETY JUDGE

Focused specifically on detecting unsafe, harmful, or policy-violating outputs. Use alongside a quality judge when safety is a concern.
When to use: Any deployment where the model interacts with end users and content safety is a requirement.

DOMAIN-SPECIFIC CORRECTNESS JUDGE

Evaluates factual correctness against a ground truth reference. Useful for tasks like question answering where a correct answer exists. Every example in the evaluation dataset must include ground_truth_answer in its metadata.
When to use: Q&A tasks or any workflow with ground truth to compare against.

TIPS

  • Set inferenceTemperature: 0.0 for judge models. You want deterministic scoring, not creative variation.
  • Use dataFields carefully: every example must include each key in its metadata; values are the titles shown to the judge.
  • Keep prompts focused: judges with 2-3 scoring criteria produce more reliable results than judges with many criteria in a single prompt.
  • Keep the default EXCLUDE_THINKING mode unless the judge needs to assess both reasoning and the final response. In that case, use THINKING_AND_RESPONSE.