Triple
T28899115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghosts 'n Goblins |
E732905
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | run-and-gun platform game series |
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: run-and-gun platform game series Context triple: [Ghosts 'n Goblins, instanceOf, run-and-gun platform game series]
-
A.
run and gun game series
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.
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.
-
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.
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.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
Created at: April 28, 2026, 8:01 a.m.