Triple
T7968930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrow Development |
E185275
|
entity |
| Predicate | spaceMountainTrackType |
P63190
|
FINISHED |
| Object | steel enclosed roller coaster |
—
|
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: steel enclosed roller coaster | Statement: [Arrow Development, spaceMountainTrackType, steel enclosed roller coaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceMountainTrackType Context triple: [Arrow Development, spaceMountainTrackType, steel enclosed roller coaster]
-
A.
rollerCoasterType
Indicates that one entity is classified as a specific type or category of roller coaster in relation to another entity.
-
B.
coasterType
chosen
Indicates the specific category or style of a coaster that characterizes its design or function.
-
C.
rideFeature
Indicates that one entity is a feature, characteristic, or component associated with a particular ride.
-
D.
skiVerticalDrop
Indicates the vertical distance in elevation from the top to the bottom of a ski run or ski area.
-
E.
spurType
Indicates the specific kind or category of spur associated with or used by an entity.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bd1c9a081909759e5bf5237204e |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:13 p.m.