Triple
T15130219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gertie the Dinosaur ice cream stand |
E361398
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disney theme park location |
C32450
|
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 location Context triple: [Gertie the Dinosaur ice cream stand, instanceOf, Disney theme park 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.
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.
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.
-
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.
Disneyland Resort facility
chosen
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.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:06 a.m.