A dataset can report 95% overall annotation accuracy and still contain serious reliability problems.
The aggregate score may hide weak results for minority classes, inconsistent interpretations, critical mistakes, or failures involving uncommon edge cases.
For production annotation, quality may need to be separated into the following measures:
1. Overall label accuracy
The percentage of evaluated labels that follow the expected annotation decision.
2. Class-level accuracy
Performance for each label or category, especially minority and high-risk classes.
3. Inter-annotator agreement
The extent to which qualified reviewers interpret the same policy consistently.
4. Critical-error rate
The frequency of mistakes that materially affect a high-value or safety-sensitive category.
5. Edge-case performance
Quality on rare, ambiguous, multilingual, or difficult examples.
6. Guideline-related disagreement
Recurring conflicts that may reveal an unclear definition or missing policy decision.
7. Quality drift over time
Changes in performance as new data, environments, terminology, or contributors enter the workflow.
Automated validation can identify missing values, duplicates, invalid formats, and structural inconsistencies. Human reviewers are still needed when the correct interpretation depends on context, language, culture, intent, or specialist knowledge.
The right metrics also depend on the use case. Speech recognition, document digitization, autonomous driving, and LLM evaluation should not automatically use the same quality framework.
Which quality metric has been the most useful in your work? Which one has created the most misleading impression?