Triple
T27026510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | runDisney |
E680802
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disney Parks event |
C9785
|
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 event Context triple: [runDisney, instanceOf, Disney Parks event]
-
A.
Disneyland Resort event
A Disneyland Resort event is a scheduled, themed experience or gathering held within the Disneyland Resort that offers guests specialized entertainment, activities, or services beyond regular park operations.
-
B.
Walt Disney World event
chosen
A Walt Disney World event is a scheduled, themed experience or celebration held within the Walt Disney World Resort that offers guests specialized entertainment, activities, and/or services beyond regular park operations.
-
C.
Walt Disney World event
A Walt Disney World event is a scheduled, themed experience or celebration held within the Walt Disney World Resort that offers guests specialized entertainment, activities, and attractions beyond regular park operations.
-
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 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.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 7:11 a.m.