Triple
T7970261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Thunder Ranch |
E185304
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defunct Disneyland attraction |
C8768
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: defunct Disneyland attraction Context triple: [Big Thunder Ranch, instanceOf, defunct Disneyland attraction]
-
A.
defunct amusement park
A defunct amusement park is a once-operational entertainment venue featuring rides and attractions that has been permanently closed, often leaving behind abandoned structures and nostalgic remnants of its former activity.
-
B.
Walt Disney World Railroad station
A Walt Disney World Railroad station is a themed train stop within the Magic Kingdom where guests board and disembark vintage-style steam trains that circle the park.
-
C.
amusement park attraction
chosen
An amusement park attraction is a designed entertainment feature or ride that provides guests with thrilling, enjoyable, or immersive experiences within a themed recreational setting.
-
D.
Universal Parks & Resorts attraction
A Universal Parks & Resorts attraction is an entertainment experience—such as a ride, show, or interactive area—designed and operated by Universal within its theme parks to immerse guests in stories, characters, and worlds from its intellectual properties and partner franchises.
-
E.
theme park attraction vehicle
A theme park attraction vehicle is a specially designed conveyance that transports guests through a ride experience, integrating safety systems, thematic elements, and motion to support the attraction’s narrative and sensory effects.
- F. None of above.
Provenance (1 batch)
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. |
Created at: March 30, 2026, 5:13 p.m.