Triple
T29247026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ikari Warriors series |
E741466
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | run-and-gun game series |
C24625
|
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: run-and-gun game series Context triple: [Ikari Warriors series, instanceOf, run-and-gun game series]
-
A.
run and gun game series
chosen
A run and gun game series is a collection of fast-paced action games focused on continuous forward movement and shooting, often featuring challenging levels, numerous enemies, and arcade-style gameplay.
-
B.
action-adventure game series
An action-adventure game series is a collection of related video games that blend real-time combat, exploration, and puzzle-solving within a continuous narrative universe or recurring thematic framework.
-
C.
arcade game series
An arcade game series is a collection of related coin-operated video games sharing common themes, characters, or gameplay mechanics, typically released over time as sequels or spin-offs.
-
D.
handheld electronic game series
A handheld electronic game series is a collection of related portable, self-contained electronic games sharing common branding, themes, or gameplay elements, typically designed for play on dedicated handheld devices.
-
E.
third-person shooter series
A third-person shooter series is a collection of related video games in which players control a character viewed from a perspective outside and behind the avatar, focusing on ranged combat and action-oriented gameplay across multiple installments.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 12:33 p.m.