Annotation guidelines are the real deliverable
Two annotators disagreeing about the same example is not a training problem. It is a definitions problem, and it is far cheaper to solve before collection than after.
Insights
What we have learned about specification, annotation and quality β written for the people who have to make these decisions.
8 articles
Two annotators disagreeing about the same example is not a training problem. It is a definitions problem, and it is far cheaper to solve before collection than after.
Egocentric footage preserves attention, approach and sequence β spatial context that third-person capture quietly discards.
Most annotator disagreement in video happens when an object is partly hidden. Deciding that once, in writing, is what keeps a track coherent.
How you write numbers, hesitation and overlap is not a detail. It is a decision the entire corpus inherits, and changing it later means starting again.
Persistent disagreement on the same kind of example is almost never carelessness. It is a label set that cannot be applied consistently.
Generated data is genuinely useful for coverage and for privacy-constrained domains. It is not a substitute for the real-world anchor.
The most common mistake is committing to volume before the specification has been tested. A small end-to-end pass costs less and tells you more.
A single agreement score is a weak summary of a rich signal. What matters is where the disagreement sits and whether it is structured.
Tell us what youβre building, what data you need and the scale of your project.