Triple
T37666289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo 3DS Game Card |
E937826
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nintendo proprietary format |
C29644
|
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 proprietary format Context triple: [Nintendo 3DS Game Card, instanceOf, Nintendo proprietary format]
-
A.
Nintendo 64 hardware variant
A Nintendo 64 hardware variant is a specific version of the Nintendo 64 console distinguished by differences in physical design, internal components, regional specifications, or bundled features while remaining compatible with the same software library.
-
B.
Nintendo Vs. System game
A Nintendo Vs. System game is an arcade title released on Nintendo’s Vs. System hardware, typically an adapted or enhanced version of an existing NES game designed for competitive or coin-operated play.
-
C.
game cartridge format
chosen
A game cartridge format is a standardized physical and data specification that defines how video game software is stored, accessed, and interfaced between a cartridge and a compatible gaming system.
-
D.
Nintendo GameCube game
A Nintendo GameCube game is a video game designed to run on Nintendo's GameCube console, typically distributed on mini-DVD discs and utilizing the system's unique controller and hardware capabilities.
-
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.
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.