Data annotation notes

From Helpful
(Redirected from Data annotation tools)
Jump to navigation Jump to search

✎ This article/section is a stub — some half-sorted notes, not necessarily checked, not necessarily correct. Feel free to ignore, or tell me about it.


Tools

Online, open source

label studio


doccano


ML-Annotate


brat


annotator.js


Annotation Lab (a.k.a. NLP Lab)


(mostly online or self-hosted)


datagym


LightTag


Label Your Data


prodigy


LabelBox


CVAT

GUI, open source

LabelImg

MAE (Multi-document Annotation Environment)


YEDDA


ELAN


Praat


Phon

Unsorted

ipyannotations

  • text (images overall)
  • python notebook


poplar


VGG Oxford University

  • varied


Annotation data formats

Text

CoNLL-X and CoNLL-U

✎ This article/section is a stub — some half-sorted notes, not necessarily checked, not necessarily correct. Feel free to ignore, or tell me about it.


CoNLL-U

https://universaldependencies.org/format.html
https://universaldependencies.org/format.html

Roughly:

  • three types of lines:
    • blank line, marking a sentence boundary
    • # at the start, marking sentence comments
    • word lines, which are tab-separated fields
      • ID: Word index, integer starting at 1 for each new sentence; may be a range for multiword tokens; may be a decimal number for empty nodes (decimal numbers can be lower than 1 but must be greater than 0).
      • FORM: Word form or punctuation symbol.
      • LEMMA: Lemma or stem of word form.
      • UPOS: Universal part-of-speech tag.
      • XPOS: Optional language-specific (or treebank-specific) part-of-speech / morphological tag; underscore if not available.
      • FEATS: List of morphological features from the universal feature inventory or from a defined language-specific extension; underscore if not available.
      • HEAD: Head of the current word, which is either a value of ID or zero (0).
      • DEPREL: Universal dependency relation to the HEAD (root iff HEAD = 0) or a defined language-specific subtype of one.
      • DEPS: Enhanced dependency graph in the form of a list of head-deprel pairs.
      • MISC: Any other annotation.


CoNLL-X

can be seen as an earlier version of CoNNL-U, which was similar but had different column definitions. There are uses where the two are compatible(verify)
https://aclanthology.org/W06-2920.pdf


File-extension wise, .conll often means CoNNL-X, .conllu oftne means CoNNL-U


Only half related is CoNLL-UL,



unsorted

IOB

✎ This article/section is a stub — some half-sorted notes, not necessarily checked, not necessarily correct. Feel free to ignore, or tell me about it.


IOB (Inside, Outside, Beginning), a.k.a. BIO, is a format certain annotation outputs to signify sequences of adjacent tokens, such as in entity recongition.

This seems to originate of using the chunker to also tag these, and having it output what is a separate thing that is probably just a single list of things, same length as input tokens (easier to parse, separate, than trying to mush it into a single annotation along the way).


It sends

  • B the beginning of a sequence
  • I inside sequence
  • O outside a sequence (terminating an ongoing sequence, or later not inside one)

(examples often show something like 'I-LOC' (LOC for location) - because you can push that into a single list of strings the same length of the token list you are annotating, and you can recover both variable-length chunks and and the annotated types from that single list. The below separates that a little to focus on the B/I/O/other markings)


There are actually a number of flavours of this idea.


The simplest might be IO - which basically isn't used at all, because it can't code that two different things are right next to each other.

There are actually surprisingly few cases where this really matters for NER, just because most aren't directly adjacent to each other, but why build in that limitation?

So an approach with three markings (IOB) seems the default.


In IOB, The difference between I and B comes in part to let you annotate that there are separate adjacent things.

For example, doing NER tagging might output: 

Los          I   LOC
Angeles      I   LOC
in           O
California   I   LOC

...which implies that Los Angeles belongs together, and the seprate in/O implies that California is a different thing. If someone removed that 'in' (and were bad at adding punctiation) then you might want to annotate like: 

Los          I   LOC
Angeles      I   LOC
California   B   LOC

to signify Los Angeles and California are separate things.


IOB2 seems to refer to the variant that would equivalently do that like: 

Los          B   LOC
Angeles      I   LOC
in           O
California   B   LOC

and 

Los          B   LOC
Angeles      I   LOC
California   B   LOC


There is also the addition of

  • L or E to signify Last/Ending in a compound
  • S or U to signify Single-token entity (or 'Unit')


So now there is

  • IOE, IOE2: delimits adjacent things by putting E on the last token of the previous
  • BIOES and BILOU where we might annotate like
Alex    S   PER
is      O
going   O
with    O
Marty   B   PER
A.      I   PER
Rick    E   PER
to      O
Los     B   LOC
Angeles E   LOC
  • "START/END" might refer to BIOES?


  • BWEMO is similar, with different naming:
B beginning-of-entity
W single-token entity
E end-of-entity
M mid-entry
O outide
  • BWEMO+ is similar to BWEMO but the rules of interpretation are expanded/relaxed, because it was made for a model where the output doesn't have strict memory of adjacency(verify)


https://en.wikipedia.org/wiki/Inside%E2%80%93outside%E2%80%93beginning_(tagging)

https://spacy.io/usage/linguistic-features#accessing-ner

https://en.wikipedia.org/wiki/Inside%E2%80%93outside%E2%80%93beginning_(tagging)

https://datascience.stackexchange.com/questions/37824/difference-between-iob-and-iob2-format

https://web.archive.org/web/20170805150451/https://lingpipe-blog.com/2009/10/14/coding-chunkers-as-taggers-io-bio-bmewo-and-bmewo/

Retrieved from "https://helpful.knobs-dials.com/index.php?title=Data_annotation_notes&oldid=95403"