Triple
T36151595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AVL tree |
E1045598
|
entity |
| Predicate | supportsTraversalOrder |
P133021
|
FINISHED |
| Object | in-order |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: in-order | Statement: [AVL tree, supportsTraversalOrder, in-order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTraversalOrder Context triple: [AVL tree, supportsTraversalOrder, in-order]
-
A.
requiresTraversalDirection
Indicates that a relationship or process can only be correctly followed or applied when moving through a structure in a specified direction.
-
B.
usesTraversal
Indicates that one entity performs or relies on a traversal process or path to interact with, reach, or operate on another entity.
-
C.
hasTraverse
Indicates that one entity moves through, across, or along the extent of another entity or space.
-
D.
enablesTraversal
Indicates that one entity provides the means or capability for another entity to move through, across, or along something.
-
E.
sortingOrderSupport
chosen
Indicates whether a system or component supports arranging items according to a specified sorting order.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.