Triple
T36151584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AVL tree |
E1045598
|
entity |
| Predicate | hasRotationType |
P7284
|
FINISHED |
| Object | single right rotation |
—
|
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: single right rotation | Statement: [AVL tree, hasRotationType, single right rotation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRotationType Context triple: [AVL tree, hasRotationType, single right rotation]
-
A.
hasRotation
Indicates that one entity is rotated with respect to another, or possesses a specific rotational orientation or motion.
-
B.
hasRotationCharacteristic
Indicates that one entity possesses a specific rotational property, behavior, or attribute in relation to another entity or reference frame.
-
C.
isRotational
Indicates that one entity moves, transforms, or is oriented by rotating around a point, axis, or center relative to another.
-
D.
hasRotationFrequency
Indicates that one entity possesses or is characterized by a specific rate at which it rotates over time.
-
E.
rotationType
chosen
Indicates the specific kind or mode of rotational movement or orientation applied in a given context.
- 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_69feb8e856d48190aa34ad8ee8376e1c |
completed | May 9, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_69feb82a2b6c8190a473cc25976897be |
completed | May 9, 2026, 4:29 a.m. |
Created at: May 3, 2026, 4:08 p.m.