Triple
T29871232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo GameCube games on Wii |
E758599
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | video game compatibility feature |
C24455
|
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 compatibility feature Context triple: [Nintendo GameCube games on Wii, instanceOf, video game compatibility feature]
-
A.
video game console compatibility mode
chosen
Video game console compatibility mode is a system feature that allows a console to run games or software designed for earlier hardware generations or different system configurations by emulating or adapting their behavior.
-
B.
video game console add-on
A video game console add-on is an auxiliary hardware device or module that connects to a game console to expand its capabilities, such as adding new input methods, enhanced graphics, storage, or additional gameplay features.
-
C.
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.
-
D.
video game console hardware platform
A video game console hardware platform is a specialized computing system designed to run games and related software, defined by its architecture, performance capabilities, and compatibility with specific titles and peripherals.
-
E.
video game
A video game is an interactive digital entertainment experience in which players engage with visual and audio content through input devices to achieve goals, overcome challenges, or explore virtual worlds.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:53 p.m.