Description
Crosswalk supplied inclusive entity-span endpoints to an exclusive end.
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.
Crosswalk supplied inclusive entity-span endpoints to an exclusive end.
When to use this tool
Use Entity Span Inclusive Exclusive Crosswalk when you already have startIndex, endIndexInclusive and need to crosswalk supplied inclusive entity-span endpoints to an exclusive end.
How to use the tool and how it works
- Enter startIndex, endIndexInclusive. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read endIndexExclusive, tokenCount. Use the output convention below.
Require nonnegative safe start, inclusive end>=start and end<=MAX_SAFE_INTEGER-1; exclusive=end+1, tokenCount=end-start+1.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| startIndex | Start Index | Required. Safe integer; minimum 0. |
| endIndexInclusive | Included final token index no greater than MAX_SAFE_INTEGER-1; the exported exclusive end adds one. | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| endIndexExclusive | End Index Exclusive | Required. Safe integer. |
| tokenCount | Token Count | Required. Safe integer. |
{
"input": {
"startIndex": 3,
"endIndexInclusive": 5
},
"output": {
"endIndexExclusive": 6,
"tokenCount": 3
}
}Limitations and assumptions
- A single indexed token counts one. No tokenization, source bound, entity identity or valid annotation is checked.
- 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.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
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
Similar or alternative tools
- Corpus Character Offset Newline Adjustment
Adjust a supplied source offset for preceding one-unit newline expansions.
- Translation Omission Span Length
Count a supplied half-open translation omission token span.