Triple
T19990720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Top Thrill Dragster |
E494054
|
entity |
| Predicate | surpassedIn |
P42712
|
FINISHED |
| Object | height record |
—
|
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: height record | Statement: [Top Thrill Dragster, surpassedIn, height record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surpassedIn Context triple: [Top Thrill Dragster, surpassedIn, height record]
-
A.
surpasses
chosen
Indicates that one entity exceeds or goes beyond another in degree, quality, performance, or achievement.
-
B.
surpassedStructure
Indicates that one entity has exceeded or gone beyond another entity in terms of structural capacity, performance, or advancement.
-
C.
overtook
Indicates that one entity moved past and ahead of another that was previously in front, typically while both were in motion.
-
D.
overcomes
Indicates that one entity successfully prevails against, defeats, or gains control over another entity or opposing force.
-
E.
wasAbove
Indicates that one entity was positioned at a higher vertical level than another entity at some point in time.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65fe00b908190bda6b9a3a3281ec0 |
completed | April 20, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:31 p.m.