Classification match
Classification match checks that a predicted label equals the expected label after normalisation. It mirrors UiPath's Binary and Multiclass classification evaluators and is the per-item input to accuracy, precision, recall and F1.
What the evaluator does
Normalise and compare. Aggregate the results into a confusion matrix to get precision, recall and F1 per class.
billing
billing
Reach for it when
- Intent routing, sentiment, ticket categorisation, any labelling task.
- Building precision/recall dashboards per class.
Not the right tool when
- Labels are free text (use answer_similarity).
Watch out for
- Label vocabularies must match exactly (Billing vs billing is handled, billing vs payments is not).
What to send
score 0–1 computed in code, label, passed at an evaluator-specific threshold, no probabilities.
{
"evaluators": [
"classification"
],
"input": "Classify: 'My card was charged twice.'",
"output": "billing",
"expected": "billing"
}Correct.
Aggregate with
One result per item is a fact; a dataset of them is a metric. These are the aggregations that fit this evaluator's output shape.
Accuracy is the share of items the evaluator got right.
Precision is the share of predicted positives that were really positive; recall is the share of real positives the evaluator caught; F1 is their harmonic mean, which is only high when both are.
A confusion matrix counts, for a binary or multiclass check, how often each true label was predicted as each label: true positives, false positives, false negatives and true negatives.
Cohen's kappa measures agreement between two raters (an evaluator and a human, or two evaluators) after subtracting the agreement you would expect by chance.
- How do I get precision and recall from classification results?
- Aggregate the per-item matches into a confusion matrix; jeval's metrics pages show the formulas with a live widget.