Triple
T1851084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D23 Expo 2017 |
E41394
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disney fan event |
C2657
|
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 fan event Context triple: [D23 Expo 2017, instanceOf, Disney fan event]
-
A.
fan convention
chosen
A fan convention is a large organized gathering where enthusiasts of specific media, genres, or hobbies come together to celebrate, meet creators and celebrities, attend panels and activities, and connect with fellow fans.
-
B.
Disney Legend
A Disney Legend is an individual honored by The Walt Disney Company for making extraordinary and lasting contributions to its legacy in fields such as animation, film, television, music, or theme parks.
-
C.
Universal Studios Japan attraction
A Universal Studios Japan attraction is an entertainment experience within the theme park—such as a ride, show, or interactive area—based on popular films, characters, or franchises, designed to immerse guests through themed environments and storytelling.
-
D.
media franchise
A media franchise is a collection of related creative works and products—such as films, TV shows, books, games, and merchandise—built around shared characters, settings, or storylines and managed as a unified commercial property.
-
E.
science fiction convention
A science fiction convention is a organized gathering of fans, creators, and industry professionals celebrating science fiction and related genres through panels, screenings, cosplay, merchandise, and community activities.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:33 p.m.