Triple
T15934559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DisneyStyle |
E386407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disney-branded store |
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-branded store Context triple: [DisneyStyle, instanceOf, Disney-branded store]
-
A.
Disney brand
The Disney brand is a globally recognized entertainment and media identity that represents family-friendly storytelling, beloved characters, immersive experiences, and nostalgic magic across films, television, theme parks, merchandise, and digital platforms.
-
B.
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.
-
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.
Disney media franchise setting
A Disney media franchise setting is a cohesive fictional world or universe, originating from Disney properties, that provides the shared backdrop, rules, and locations for interconnected stories, characters, and media products.
-
E.
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.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:53 a.m.