Triple
T31601771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TransCenter |
E806365
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Epcot attraction component |
C47016
|
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: Epcot attraction component Context triple: [TransCenter, instanceOf, Epcot attraction component]
-
A.
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.
-
B.
Epcot character
An Epcot character is a themed persona or mascot that embodies the cultures, stories, or futuristic concepts featured in Epcot’s pavilions and attractions, interacting with guests to enhance the park’s immersive experience.
-
C.
Disney Parks technology product
A Disney Parks technology product is a digital or physical tech-based tool, system, or service designed to enhance, personalize, or manage guest experiences and operations within Disney theme parks and resorts.
-
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 resort component
chosen
A theme park resort component is an individual facility, attraction, or service (such as a park, hotel, dining, or entertainment venue) that forms part of an integrated theme park resort experience.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:33 p.m.