Triple
T24134460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frozen – Live at the Hyperion |
E598044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disney Parks live entertainment production |
C8344
|
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 Parks live entertainment production Context triple: [Frozen – Live at the Hyperion, instanceOf, Disney Parks live entertainment production]
-
A.
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.
-
B.
Disney entertainment production
Disney entertainment production is the process by which The Walt Disney Company develops, finances, and creates films, television shows, stage productions, and related media content under its various brands and studios.
-
C.
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.
-
D.
theme park show
chosen
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.
-
E.
Disney establishment
A Disney establishment is any physical or virtual venue, facility, or location owned, operated, licensed, or branded by The Walt Disney Company that provides entertainment, retail, hospitality, or related services.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:26 p.m.