Triple
T8211147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney California Adventure Food & Wine Festival |
E191818
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disney theme park event |
C11205
|
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 event Context triple: [Disney California Adventure Food & Wine Festival, instanceOf, Disney theme park event]
-
A.
Disneyland Resort event
chosen
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
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 resort complex
A Disney resort complex is a large, themed vacation destination that combines multiple hotels, entertainment venues, dining, shopping, and recreational facilities centered around Disney parks and experiences.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:44 p.m.