Triple
T1629737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Mountain |
E35229
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disney theme park attraction |
C6497
|
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: Disney theme park attraction Context triple: [Space Mountain, instanceOf, Disney theme park attraction]
-
A.
Universal Studios Japan attraction
A Universal Studios Japan attraction is an entertainment experience within the theme park—such as a ride, show, or interactive area—based on popular films, characters, or franchises, designed to immerse guests through themed environments and storytelling.
-
B.
Universal Studios Hollywood attraction
A Universal Studios Hollywood attraction is an entertainment experience within the theme park—such as a ride, show, or interactive exhibit—based on popular films, television properties, or studio-themed environments designed to immerse guests in cinematic worlds.
-
C.
EPCOT entertainment offering
An EPCOT entertainment offering is a themed attraction, show, or interactive experience within EPCOT that showcases culture, innovation, or storytelling through performances, exhibits, or immersive environments.
-
D.
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.
-
E.
theme park entertainment
Theme park entertainment encompasses the rides, shows, attractions, and interactive experiences designed to engage and delight visitors within a themed recreational environment.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:28 p.m.