Triple
T7644944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duckburg |
E173096
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disney location |
C12439
|
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 location Context triple: [Duckburg, instanceOf, Disney location]
-
A.
Disney establishment
chosen
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.
-
B.
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.
-
C.
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.
-
D.
Universal Studios Hollywood attraction
A Universal Studios Hollywood attraction is an entertainment experience within the theme park—such as a ride, show, or interactive exhibit—based on popular films, television properties, or studio-themed environments designed to immerse guests in cinematic worlds.
-
E.
Universal Studios attraction area
A Universal Studios attraction area is a themed section of the park that groups together rides, shows, shops, and dining experiences based on a specific movie, franchise, or concept to create an immersive entertainment environment.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:58 p.m.