Triple
T19791187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game Developers Conference |
E475412
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | video game industry event |
C42629
|
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: video game industry event Context triple: [Game Developers Conference, instanceOf, video game industry event]
-
A.
video game organization
A video game organization is a structured entity that manages the development, publishing, promotion, or competitive play of video games through coordinated teams, resources, and strategic planning.
-
B.
video game industry figure
A video game industry figure is an individual who significantly influences the creation, development, publishing, or cultural impact of video games through roles such as designer, developer, executive, critic, or content creator.
-
C.
film industry event
A film industry event is a planned gathering where professionals and stakeholders in cinema come together for activities such as premieres, festivals, markets, awards, or conferences related to the creation, promotion, and distribution of films.
-
D.
music industry event
A music industry event is a planned gathering where artists, professionals, and stakeholders in the music business come together for performances, networking, promotion, and industry-related activities.
-
E.
fan convention
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.
- F. None of above. chosen
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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:49 p.m.