Triple
T37665628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Switch 2 |
E937813
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | successor console |
C8189
|
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: successor console Context triple: [Switch 2, instanceOf, successor console]
-
A.
successor state
A successor state is a new system configuration that directly results from applying a specific action or transition to a current state within a defined process or model.
-
B.
seventh-generation video game console
A seventh-generation video game console is a home or handheld gaming system released roughly between 2005 and 2012 that introduced widespread HD graphics, online gaming services, motion controls, and multimedia capabilities beyond traditional gameplay.
-
C.
successor companies
Successor companies are organizations that emerge from, replace, or continue the operations, assets, or legal identity of a predecessor business following events such as mergers, acquisitions, restructurings, or dissolutions.
-
D.
eighth-generation video game console
chosen
An eighth-generation video game console is a home or handheld gaming system released roughly between 2012 and 2017, featuring HD or higher graphics, robust online services, and support for digital distribution and multimedia entertainment.
-
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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.