Triple
T13507266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | splay tree |
E321044
|
entity |
| Predicate | invariant |
P29145
|
FINISHED |
| Object | inorder traversal yields keys in sorted 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: inorder traversal yields keys in sorted order | Statement: [splay tree, invariant, inorder traversal yields keys in sorted order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invariant Context triple: [splay tree, invariant, inorder traversal yields keys in sorted order]
-
A.
invariantOf
chosen
Indicates that one element is an invariant (a property or quantity that remains unchanged) with respect to another element, system, or transformation.
-
B.
invariantUnder
Indicates that a property, structure, or quantity remains unchanged when a specified transformation or operation is applied.
-
C.
invariantType
Indicates that one entity has a type or classification that remains constant or unchanged under specified conditions or transformations.
-
D.
constant
Indicates that the relationship or value does not change across different instances, contexts, or over time.
-
E.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf8259a08190ada13c4a3078f07d |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.