OVERVIEW
The following describes the request schema used to create judge and rubric evaluators in Oumi, including:- Metadata about the evaluator
- Evaluation parameters
- Model configuration
- Scoring settings
Fields marked with (*) are required.
SCHEMA STRUCTURE
DISPLAYNAME *
Human-readable name of the evaluator.PROPERTIES
CONSTRAINTS
EXAMPLE
JUDGE PARAMS *
Defines the evaluation parameters and scoring behavior.PROPERTIES
EVALUATORTYPE
Defines the evaluator mechanism.PROMPT *
Prompt provided to the evaluator model to guide scoring behavior.CONSTRAINTS
EXAMPLE
JUDGMENTSCORES
Maps each allowed judgment label to a score from0.0 to 1.0. The example below defines a boolean judge.
Example structure:
DATAFIELDS
Defines the dataset fields that are used by the evaluator. Every evaluation example must include each configured field in its metadata. Example structure:RUBRIC JUDGE PARAMS
A rubric evaluator uses the same parameters as a judge evaluator, exceptjudgmentScores. Instead, it defines criteria, each with its own labels and scores, and an aggregation that combines them. See Creating a rubric evaluator.
PROPERTIES
CRITERIA *
Each criterion is one question the judge answers.
Each label is an object with a
label and an optional score from 0.0 to 1.0. A label without a score is allowed but does not count toward the overall score, which suits values such as not_applicable.
CONSTRAINTS
AGGREGATION
The default isweighted_mean. Only criteria with a scored label count.
EXAMPLE
MODELIDENTIFIER *
Defines the model used by the evaluator. This object follows the Model Identifier schema. Example:INFERENCECONFIG *
Defines runtime inference behavior for the evaluator model. Example:RESPONSEFILTERMODE
Controls which parts of the model output are used for evaluation. The default isEXCLUDE_THINKING.