Triple
T29182650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arcade (Vs. Castlevania) |
E739784
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nintendo Vs. System game |
C54737
|
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: Nintendo Vs. System game Context triple: [Arcade (Vs. Castlevania), instanceOf, Nintendo Vs. System game]
-
A.
Nintendo Entertainment System game
A Nintendo Entertainment System game is a software title designed to run on the NES console, typically featuring 8-bit graphics, chiptune audio, and gameplay constrained by the system’s hardware limitations.
-
B.
Nintendo DS game
A Nintendo DS game is an interactive software title designed specifically for the dual-screen, handheld Nintendo DS system, utilizing its unique touch screen, microphone, and portable hardware capabilities for gameplay.
-
C.
Nintendo Switch game
A Nintendo Switch game is a software title designed to run on the Nintendo Switch console, providing interactive entertainment that can be played in handheld, tabletop, or docked TV mode.
-
D.
Super Nintendo Entertainment System game
A Super Nintendo Entertainment System game is a video game designed to run on Nintendo's 16-bit SNES console, typically distributed on ROM cartridges and featuring the system’s characteristic graphics, sound, and controller-based gameplay.
-
E.
Virtual Boy game
A Virtual Boy game is an interactive software title specifically designed to run on Nintendo's Virtual Boy console, utilizing its stereoscopic red-and-black 3D display and unique controller for gameplay.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 11:58 a.m.