Skip to the content.

Annotation Type Reference

A guide to the 39 annotation types used in this showcase, with example configurations for each. Potato supports more scheme types than these; the annotation types documentation has the full list.


radio

Description: Single-choice selection from a list of mutually exclusive labels, for classification tasks where exactly one option applies.

Required fields:

Example tasks:


multiselect

Description: Multi-label selection where annotators can choose one or more labels from a list. Used when multiple categories can apply simultaneously to a single item.

Required fields:

Example tasks:


text

Description: Free-text input field for open-ended responses. Used for tasks requiring written explanations, translations, captions, or any unstructured textual annotation.

Required fields:

Example tasks:


likert

Description: Ordinal rating scale for measuring degree or intensity. Produces a fixed set of ordered response levels (e.g., 1-5 stars, Strongly Disagree to Strongly Agree).

Required fields (one of):

Example tasks:


slider

Description: Continuous or semi-continuous numeric scale with a draggable handle. Used when fine-grained numeric ratings are needed rather than discrete categories.

Required fields (one of):

Example tasks:


span

Description: Text span annotation where annotators highlight words or character ranges and assign labels. Used for NER, keyphrase extraction, and other in-text markup.

Required fields:

Example tasks:


Description: Relation annotation between two text spans. Annotators first mark entity or event spans, then draw typed links between them to represent relationships such as causation, part-of, or semantic roles.

Required fields:

Example tasks:


select

Description: Dropdown selection from a list of options. Similar to radio but rendered as a dropdown menu, useful when the number of options is large and would be unwieldy as radio buttons.

Required fields:

Example tasks:


number

Description: Numeric input field for entering integer or decimal values. Used for counting, scoring, or any task requiring a precise numeric response.

Required fields:

Example tasks:


multirate

Description: Rate multiple items on the same scale simultaneously. Displays a matrix where rows are items (e.g., model responses, attributes) and columns are rating levels.

Required fields:

Example tasks:


pure_display

Description: Display-only element that shows information to the annotator without collecting any input. Used for presenting context, instructions, model cards, or reference material alongside active annotation fields.

Required fields:

Example tasks:


pairwise

Description: Side-by-side comparison of two items where annotators judge which is better, or rate relative quality. Used for preference learning and RLHF data collection.

Required fields:

Example tasks:


bws (Best-Worst Scaling)

Description: Best-Worst Scaling (MaxDiff) annotation where annotators select the best and worst items from a set. Produces more reliable rankings than direct rating by reducing scale bias.

Required fields:

Example tasks:


image_annotation

Description: Spatial annotation on images using drawing tools such as bounding boxes, polygons, freeform regions, landmarks, and brushes. Used for object detection, segmentation, keypoint annotation, and region labeling.

Required fields:

Example tasks:


audio_annotation

Description: Temporal segment annotation on audio waveforms. Annotators mark time-aligned regions in audio and assign labels, useful for transcription alignment, speaker diarization, and phonetic annotation.

Required fields:

Example tasks:


video_annotation

Description: Temporal segment annotation on video timelines. Annotators mark start/end times of events, actions, or scenes within a video and assign labels to each segment.

Required fields:

Example tasks:


video (display only)

Description: Embeds a video player without collecting temporal annotations. Used when annotators need to watch video content before responding with other annotation types (radio, text, etc.).

Required fields:

Example tasks:


coreference

Description: Coreference chain annotation where annotators link mentions (pronouns, noun phrases, names) that refer to the same real-world entity into clusters. Used for entity and event coreference resolution.

Required fields:

Example tasks:


tree_annotation

Description: Hierarchical tree structure annotation where annotators build parent-child relationships between nodes. Used for syntactic parsing, discourse structure, and any task requiring tree-shaped output.

Required fields:

Example tasks:


triage

Description: Quick pre-annotation filtering step where annotators flag whether an item needs detailed annotation. Speeds up a pipeline by letting annotators skip irrelevant items before the more expensive schemes run.

Required fields:

Example tasks:


event_annotation

Description: Structured event extraction annotation where annotators identify event triggers, arguments, and roles within text. Used for tasks that mark event structures with typed participants.

Required fields:

Example tasks:


tiered_annotation

Description: Multi-level hierarchical annotation where annotators assign labels at multiple tiers (e.g., topic then subtopic, coarse then fine category). Each tier can have its own label set.

Required fields:

Example tasks:


ranking

Description: Rank a set of items from best to worst. Produces a full or partial ordering rather than an absolute score.

Required fields:

Example tasks:


semantic_differential

Description: Rating on bipolar adjective scales anchored by opposing terms at each end (e.g., Fake – Natural). The standard instrument format in psychometrics and human–robot interaction research.

Required fields:

Example tasks:


conjoint

Description: Discrete-choice conjoint analysis: annotators choose between side-by-side profiles whose attributes are independently randomized, so that each attribute’s causal effect on choice can be estimated.

Required fields:

Example tasks:


soft_label

Description: Distribute a fixed budget of probability mass across labels instead of picking one. Useful when annotators are uncertain, or when the disagreement itself is the signal you want to keep.

Required fields:

Example tasks:


rubric_eval

Description: Score a response against a list of named rubric criteria, each on its own scale. Used for fine-grained, skill-decomposed evaluation of model outputs.

Required fields:

Example tasks:


error_span

Description: Mark spans of text as errors, assigning each a typed error category and a severity. The standard format for translation and generation quality error analysis.

Required fields:

Example tasks:


text_edit

Description: Inline editing of a source text with diff tracking. Annotators rewrite rather than label, and the interface records what changed.

Required fields:

Example tasks:


hierarchical_multiselect

Description: Multi-label selection over a nested taxonomy, with expandable parent/child nodes, search, and optional automatic propagation of selections up or down the hierarchy.

Required fields:

Example tasks:


multi_document_event

Description: Annotate events that recur across multiple documents, filling structured slots per event and linking mentions to shared cross-document event instances.

Required fields:

Example tasks:


speech_transcript

Description: Per-segment annotation over a time-aligned transcript: tag speech errors or disfluencies on each segment, optionally supplying a correction, with audio playback per segment.

Required fields:

Example tasks:


temporal_grounding

Description: Mark gold time intervals in a video that correspond to a natural-language query, with live IoU feedback against predicted moments.

Required fields:

Example tasks:


table_grid

Description: Table structure annotation over an image: define the row and column grid, then assign each cell a role such as header, data, or empty.

Required fields:

Example tasks:


process_reward

Description: Per-step reward signals over a reasoning or action trace, used to train and evaluate process reward models. Supports full per-step rating and first-error localization modes.

Required fields:

Example tasks:


gui_trajectory

Description: Step-by-step review of a computer-use or GUI agent episode: each step shows a screenshot and the action taken, and annotators judge action correctness and click grounding.

Required fields:

Example tasks:


tool_call_review

Description: Per-tool-call correctness review over an agent dialogue: was the right tool selected, were the arguments right, and was the call made in the right order.

Required fields:

Example tasks:


failure_attribution

Description: Attribute a multi-agent system’s failure to a responsible agent and a decisive step, with a free-text reason. Localizes blame rather than scoring overall quality.

Required fields:

Example tasks:


agent_scorecard

Description: Per-agent and per-team scorecard over a multi-agent run: rate each agent and the team on named dimensions, and check off which run milestones were reached.

Required fields:

Example tasks: