Triple
T13507249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | splay tree |
E321044
|
entity |
| Predicate | balancingMethod |
P28297
|
FINISHED |
| Object | tree rotations during splaying |
—
|
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: tree rotations during splaying | Statement: [splay tree, balancingMethod, tree rotations during splaying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: balancingMethod Context triple: [splay tree, balancingMethod, tree rotations during splaying]
-
A.
aimsToBalance
Indicates an intention or effort by one entity to bring multiple elements, forces, or conditions into a state of equilibrium.
-
B.
forceBalance
Indicates that the net forces acting on an entity or system are in equilibrium, resulting in no overall acceleration.
-
C.
weightingMethod
Indicates how relative importance or influence is assigned to elements within a set, such as criteria, features, or data points, in a calculation or decision process.
-
D.
powerBalance
Indicates the relative distribution of power or influence between entities in a relationship or interaction.
-
E.
tuningMethod
chosen
Indicates the method or approach used to adjust or optimize something’s parameters or performance.
- 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.