Triple
T13645649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audio-Animatronics |
E326094
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disney technology |
C23329
|
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 technology Context triple: [Audio-Animatronics, instanceOf, Disney technology]
-
A.
Disney Parks technology product
chosen
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 digital service
A Disney digital service is an online platform or application provided by The Walt Disney Company that delivers entertainment, content, or interactive experiences to users via internet-connected devices.
-
C.
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.
-
D.
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.
-
E.
Disney brand
The Disney brand is a globally recognized entertainment and media identity that represents family-friendly storytelling, beloved characters, immersive experiences, and nostalgic magic across films, television, theme parks, merchandise, and digital platforms.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:51 p.m.