Triple
T5148806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyper Coaster |
E116139
|
entity |
| Predicate | exceeds |
P42712
|
FINISHED |
| Object | traditional coaster height benchmarks |
—
|
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: traditional coaster height benchmarks | Statement: [Hyper Coaster, exceeds, traditional coaster height benchmarks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exceeds Context triple: [Hyper Coaster, exceeds, traditional coaster height benchmarks]
-
A.
surpasses
chosen
Indicates that one entity exceeds or goes beyond another in degree, quality, performance, or achievement.
-
B.
canBeExceededIn
Indicates that one entity’s value, level, or extent is capable of being surpassed by that of another entity within a specified context.
-
C.
reaches
Indicates that one entity extends or moves until it makes contact with, attains, or arrives at another entity or point.
-
D.
holdsOver
Indicates that a certain condition, state, or relationship remains valid or continues to apply across a specified period, context, or range.
-
E.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
- 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_69bd4446c0e08190a7c29dc74976bf03 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd78d7f4d081908d59adcd86f52f1d |
completed | March 20, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69bd77ae2f10819098bb8939106e1281 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:43 p.m.