Skip to content

Main content

CoNLL-U Decimal Empty Node Key

Split a CoNLL-U empty-node ID without parsing its dot suffix as a fractional decimal or checking sentence-order constraints.

Loading tool…

Description

Split a supplied CoNLL-U-style decimal empty-node ID.

Language-processing records distinguish tokens, code points, UTF-16 positions and UTF-8 byte offsets. Tag grammars and local transition checks do not validate a full annotation sequence. Log-loss units determine perplexity conversion, while identifier suffixes may be textual labels rather than ordinary decimal numbers.

Split a supplied CoNLL-U-style decimal empty-node ID.

When to use this tool

Use CoNLL-U Decimal Empty Node Key when you already have emptyNodeId and need to split a supplied CoNLL-U-style decimal empty-node ID.

How to use the tool and how it works

  1. Enter emptyNodeId. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read anchorWordId, suffixText. Use the output convention below.

Require anchor 0 or a nonzero-leading positive integer, dot, and nonzero-leading positive suffix digits. Convert only the anchor to a safe integer and preserve suffixText exactly.1

CoNLL-U empty nodes use an anchor and a positive integer suffix; a pre-first-word anchor can be zero. These are identifiers, not decimal-valued positions.2

Input fieldMeaning and unitsAccepted input
emptyNodeIdEmpty Node IdRequired. Text; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
anchorWordIdNonnegative safe integer word anchor; zero is accepted for pre-first-word empty nodes.Required. Safe integer.
suffixTextPositive digit suffix preserved as text, including its length; 5.10 and 5.1 are distinct identifiers.Required. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "emptyNodeId": "4.10"
  },
  "output": {
    "anchorWordId": 4,
    "suffixText": "10"
  }
}

Limitations and assumptions

  • This is an identifier, not a decimal fraction; suffix 10 differs from 1. No suffix numeric range, sentence, anchor existence, ordering or complete empty-node record is validated.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Validate the complete corpus format, tokenizer, annotation sequence and scoring convention. Use a full parser or model evaluation when needed, preserving the exact offset unit, vocabulary and log base rather than inferring them from a local transformation.

References

  1. Calculation and input contract: computational-linguistics/conllu-decimal-empty-node-key — tool.io

  2. CoNLL-U Format: Word, range and empty-node identifiers — Universal Dependencies

Similar or alternative tools