Triple
T35288419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pixar Pals |
E1019154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disneyland Resort offering |
C23580
|
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 Resort offering Context triple: [Pixar Pals, instanceOf, Disneyland Resort offering]
-
A.
Walt Disney World Resort offering
A Walt Disney World Resort offering is any product, service, or experience—such as accommodations, theme park access, dining, entertainment, or vacation packages—provided under the Walt Disney World Resort brand to enhance guests’ visits.
-
B.
Disneyland entertainment offering
chosen
A Disneyland entertainment offering is a themed, time-bound experience—such as a show, parade, character encounter, or seasonal event—designed to engage guests through storytelling, performance, and interaction within the park.
-
C.
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.
-
D.
Disneyland Resort facility
A Disneyland Resort facility is any physical location, structure, or venue within the Disneyland Resort that supports guest experiences, operations, entertainment, lodging, dining, or 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.