Triple
T13507208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fibonacci heap |
E321043
|
entity |
| Predicate | rootListStructure |
P13436
|
FINISHED |
| Object | doubly linked list |
—
|
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: doubly linked list | Statement: [Fibonacci heap, rootListStructure, doubly linked list]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rootListStructure Context triple: [Fibonacci heap, rootListStructure, doubly linked list]
-
A.
rootStructure
chosen
Indicates that one entity serves as the primary or foundational structural element upon which another entity is based or organized.
-
B.
rootSystem
Indicates that one entity is the primary or foundational source from which another entity originates, grows, or is structurally anchored.
-
C.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
-
D.
lapStructure
Indicates that one entity forms a lap-like structural surface or support upon which another entity can rest or be positioned.
-
E.
organizationalRoots
Indicates that one organization originates from, was founded by, or structurally grows out of another organization.
- 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.