Triple
T29871384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wii Message Board |
E758602
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wii system software feature |
C56374
|
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: Wii system software feature Context triple: [Wii Message Board, instanceOf, Wii system software feature]
-
A.
Nintendo 3DS hardware feature
A Nintendo 3DS hardware feature is a specific built-in component or capability of the Nintendo 3DS system—such as its stereoscopic 3D display, cameras, motion sensors, or wireless connectivity—that enables particular forms of interaction, gameplay, or system functionality.
-
B.
Wii U game
A Wii U game is a software title designed to run on Nintendo's Wii U console, often utilizing its unique GamePad controller for dual-screen and motion-based gameplay experiences.
-
C.
Nintendo 3DS feature
A Nintendo 3DS feature is a distinct hardware or software capability of the Nintendo 3DS system that enhances gameplay, interaction, or user experience (such as stereoscopic 3D, StreetPass, or the touchscreen interface).
-
D.
Nintendo network service
A Nintendo network service is an online platform provided by Nintendo that enables digital distribution, multiplayer connectivity, account management, and related online features for Nintendo gaming systems and software.
-
E.
PlayStation Network feature
A PlayStation Network feature is a distinct online service or functionality within the PlayStation ecosystem that enhances user interaction, content access, or gameplay experiences across connected PlayStation devices.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:53 p.m.