Triple
T9733413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biergarten Restaurant |
E235999
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Walt Disney World dining location |
C10131
|
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: Walt Disney World dining location Context triple: [Biergarten Restaurant, instanceOf, Walt Disney World dining location]
-
A.
Walt Disney World location
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.
Walt Disney World Resort offering
chosen
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.
-
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 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.
-
E.
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.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:22 p.m.