ToolJovia
Text

Token Span Label Workbench

Convert supplied Unicode-scalar entity spans and token boundaries to strict IOB2/BILUO labels or back.

✓ Browser-local processing
Processed in this tab. Up to 100,000 characters unless this tool states a smaller limit.

Loading tool…

How to use Token Span Label Workbench

Inspect an annotation exchange with explicit source coordinates instead of relying on hidden tokenization. The workbench validates transitions, nonoverlap and exact token-edge alignment, then exports both literal token text and recovered entity spans for review.

  1. Enter input, ordered token start/end json, ordered labeled span json, tags json for reverse conversion.
  2. Choose the settings for token span label workbench, then run the tool.
  3. Review the result and any limitations before copying or downloading it.

Good to know

  • 50,000 source characters, 2,000 ordered nonoverlapping tokens, 500 entities and exact original JSON integer offsets. Coordinates count Unicode scalar values, not UTF-16 units, bytes or grapheme clusters; combining marks remain separate.
  • IOB2 and BILUO only, strict transitions and ASCII label names. Entity endpoints must be existing token edges. No NLP, automatic tokenization, nested/overlapping entities, label repair or spaCy runtime/importer claim.
  • Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.

Common questions

Does an emoji use two offset positions?

A single supplementary-plane emoji uses one Unicode scalar position here. A joined or combining sequence can use several positions. Supply coordinates using that declared convention rather than JavaScript UTF-16 length.

Is this input sent to a server?

No. The application processes this input inside your browser tab and does not save it to persistent storage.

Keep going with related tools

All text →