Triple
T15763348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donkey Kong universe |
E382153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | video game franchise setting |
C10215
|
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 franchise setting Context triple: [Donkey Kong universe, instanceOf, video game franchise setting]
-
A.
video game brand
A video game brand is a recognizable identity encompassing a series of games, characters, visual styles, and values that collectively distinguish and market a company's gaming products to consumers.
-
B.
video game
A video game is an interactive digital entertainment experience in which players engage with visual and audio content through input devices to achieve goals, overcome challenges, or explore virtual worlds.
-
C.
science fiction video game series
A science fiction video game series is a collection of related games set in futuristic or speculative worlds that explore advanced technology, space travel, alien life, or other science-based imaginative concepts through interactive storytelling and gameplay.
-
D.
platform game series
chosen
A platform game series is a collection of related video games, typically sharing characters, settings, and core mechanics, in which players navigate environments by running, jumping, and overcoming obstacles across multiple installments.
-
E.
video game namesake
A video game namesake is a person, character, place, or entity after whom a video game or its title is named, serving as the primary reference or inspiration for the game's identity.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:47 a.m.