Triple
T37554591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D.I.C.E. Summit 2017 |
E933664
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | video game industry conference |
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 conference Context triple: [D.I.C.E. Summit 2017, instanceOf, video game industry conference]
-
A.
video game industry event
chosen
A video game industry event is a planned gathering where developers, publishers, hardware makers, media, and fans come together to showcase, promote, and discuss video games, technologies, and related business opportunities.
-
B.
video game exhibition
A video game exhibition is a curated event or space where video games, their history, technology, art, and cultural impact are showcased through playable demos, displays, and interactive experiences for public engagement.
-
C.
video game presentation
A video game presentation is a structured showcase that visually and verbally highlights a game's core concepts, mechanics, aesthetics, and unique selling points to inform or persuade an audience.
-
D.
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.
-
E.
technology conference
A technology conference is a structured event where professionals, enthusiasts, and organizations gather to share knowledge, showcase innovations, and discuss trends and developments in technology.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.