Triple
T9696996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town Square (Magic Kingdom) |
E234678
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Magic Kingdom location |
C8882
|
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: Magic Kingdom location Context triple: [Town Square (Magic Kingdom), instanceOf, Magic Kingdom location]
-
A.
Walt Disney World location
chosen
A Walt Disney World location is a specific place within the Walt Disney World Resort—such as a park, attraction, resort, or dining venue—characterized by its themed environment, services, and role in the overall guest experience.
-
B.
area of Magic Kingdom
An area of Magic Kingdom is a themed land within the park that groups attractions, entertainment, dining, and decor around a cohesive story or setting.
-
C.
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.
-
D.
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.
-
E.
Disneyland entertainment offering
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.
- 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:18 p.m.