Description
Check whether two dependency arcs strictly cross.
Language-processing records depend on tokenization, indexing, null sentinels and text representation. A UTF-8 byte offset, UTF-16 index, dependency link or literal feature label can be handled precisely without inferring linguistic correctness or semantic equivalence.
Check whether two dependency arcs strictly cross.
When to use this tool
Use Dependency Projectivity Crossing Flag when checking a supplied linguistic annotation, span, alignment or text-offset convention.
How to use the tool and how it works
- Enter firstHead, firstDependent, secondHead, secondDependent. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read crosses. Inspect crosses before interpreting the associated values.
Check whether two dependency arcs strictly cross. Require nonnegative whole distinct head/dependent endpoints per arc; normalize endpoint order and test strict alternating inequalities.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| firstHead | First Head | Required. Safe integer; minimum 0. |
| firstDependent | First Dependent | Required. Safe integer; minimum 0. |
| secondHead | Second Head | Required. Safe integer; minimum 0. |
| secondDependent | Second Dependent | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| crosses | Crosses | Required. Boolean. |
{
"input": {
"firstHead": 1,
"firstDependent": 3,
"secondHead": 2,
"secondDependent": 4
},
"output": {
"crosses": true
}
}Limitations and assumptions
- Shared endpoints and nesting do not count as crossing; two arcs alone do not establish whole-tree projectivity or valid syntax.
- 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
Use the appropriate tokenizer, Unicode and annotation-format conventions and validate the complete text or tree for full linguistic processing.
References
Similar or alternative tools
- Dependency Head Distance
Return dependency head distance with a root convention.
- Alignment Null Support Share
Summarize alignment weight at supplied null indexes.