Triple
T27934752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linked Magic Key passes |
E708073
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disneyland digital pass feature |
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: Disneyland digital pass feature Context triple: [Linked Magic Key passes, instanceOf, Disneyland digital pass feature]
-
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.
official Disneyland Resort app
The official Disneyland Resort app is a mobile application that allows guests to plan and manage their visit by viewing park maps, wait times, entertainment schedules, dining options, and making reservations and Lightning Lane selections.
-
C.
Tokyo Disney Resort ticket
A Tokyo Disney Resort ticket is a time-bound admission pass that grants a guest access to specified parks, dates, and attractions within Tokyo Disney Resort under defined usage conditions.
-
D.
Disney character experience
A Disney character experience is an interactive encounter where guests meet, engage with, and often take photos or receive autographs from costumed Disney characters in themed settings.
-
E.
Disney attraction overlay
A Disney attraction overlay is a temporary or seasonal transformation of an existing ride or show, featuring new theming, story elements, audio, and visuals while retaining the original attraction’s underlying structure.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:05 p.m.