Triple
T27968758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomorrowland (Magic Kingdom) |
E704796
|
entity |
| Predicate | hasIconicRide |
P165109
|
FINISHED |
| Object | Space Mountain |
—
|
NE NERFINISHED |
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: Space Mountain | Statement: [Tomorrowland (Magic Kingdom), hasIconicRide, Space Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIconicRide Context triple: [Tomorrowland (Magic Kingdom), hasIconicRide, Space Mountain]
-
A.
hasRideSystem
Indicates that one entity (typically an attraction or ride) uses or is associated with a particular ride system or ride mechanism.
-
B.
hasThrillRides
Indicates that an entity offers or includes thrill rides as part of its features or attractions.
-
C.
hasSpinnerRide
Indicates that an entity offers, includes, or is associated with a spinner-style ride attraction.
-
D.
hasDarkRide
Indicates that one entity features or includes a dark ride attraction associated with the other entity.
-
E.
hasRailroadAttraction
Indicates that one entity features or contains a railroad-related attraction, such as a railway exhibit, ride, or point of interest.
- F. None of above. chosen
Provenance (4 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 7:36 p.m.