Triple
T7970213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Play Disney Parks app |
E185303
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theme park companion app |
C11210
|
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: theme park companion app Context triple: [Play Disney Parks app, instanceOf, theme park companion app]
-
A.
theme park entrance
The theme park entrance is the primary access point where guests transition from the outside world into the park, typically featuring ticketing, security, and iconic visual elements that establish the park’s identity and atmosphere.
-
B.
theme park service
chosen
A theme park service is an offering that enhances visitors’ experiences through entertainment, amenities, operations, and guest support within a themed recreational environment.
-
C.
theme park show
A theme park show is a live or pre-recorded entertainment performance within a theme park, designed to engage guests through storytelling, music, special effects, and character appearances that enhance the park’s overall themed experience.
-
D.
theme park setting
A theme park setting is a large, immersive entertainment environment organized around specific themes, featuring rides, attractions, performances, and themed areas designed to create a cohesive, fantastical experience for visitors.
-
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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:13 p.m.