Triple
T8552387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNK hardware |
E202473
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | video game hardware family |
C10372
|
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 hardware family Context triple: [SNK hardware, instanceOf, video game hardware family]
-
A.
gaming platform family
chosen
A gaming platform family is a group of related hardware or software gaming systems that share a common architecture, ecosystem, and compatible games and services across multiple generations or variants.
-
B.
home video game hardware
Home video game hardware is a dedicated electronic device designed to run video games on a television or display, typically using game media or digital downloads and controlled via gamepads or other input devices.
-
C.
home video game console
A home video game console is a dedicated electronic device designed to connect to a television or display and run video games using physical or digital media, typically operated with handheld controllers in a domestic setting.
-
D.
video game console brand
A video game console brand is a named product line under which a company designs, markets, and supports a family of gaming hardware systems and related services.
-
E.
sixth-generation video game console
A sixth-generation video game console is a home gaming system released around the late 1990s to early 2000s, characterized by 128-bit processing, optical disc media, and support for 3D graphics and online connectivity (e.g., PlayStation 2, Xbox, GameCube, Dreamcast).
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:19 p.m.