Triple
T20350255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA1 |
E495986
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Super Nintendo Entertainment System enhancement chip |
C43689
|
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: Super Nintendo Entertainment System enhancement chip Context triple: [SA1, instanceOf, Super Nintendo Entertainment System enhancement chip]
-
A.
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.
-
B.
Neo Geo hardware platform
The Neo Geo hardware platform is a family of high-performance arcade and home video game systems developed by SNK, known for its powerful 2D graphics, interchangeable cartridges, and long commercial lifespan.
-
C.
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.
-
D.
Famicom game
A Famicom game is a video game designed to run on Nintendo's Family Computer (Famicom) console, typically distributed on ROM cartridges and adhering to the system's hardware and technical limitations.
-
E.
Nintendo 64 game
A Nintendo 64 game is a video game designed to run on the Nintendo 64 console, typically distributed on proprietary cartridges and utilizing the system’s 3D graphics and controller features.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:24 a.m.