Triple
T15056389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverside Depot |
E379503
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disney theme park shop |
C16932
|
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 theme park shop Context triple: [Riverside Depot, instanceOf, Disney theme park shop]
-
A.
theme park shop
chosen
A theme park shop is a retail location within a theme park that sells merchandise such as souvenirs, apparel, toys, and themed collectibles related to the park’s attractions and characters.
-
B.
theme park attraction shop
A theme park attraction shop is a retail location situated near or within a specific ride or show that sells themed merchandise, souvenirs, and related products tied directly to that attraction’s story and experience.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:01 a.m.