Triple
T1892293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo Wii |
E41898
|
entity |
| Predicate | supportsGameCubeControllers |
P33107
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [Nintendo Wii, supportsGameCubeControllers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGameCubeControllers Context triple: [Nintendo Wii, supportsGameCubeControllers, true]
-
A.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
-
B.
supportsMemoryCard
Indicates that one entity is compatible with and can accept or use a memory card associated with another entity.
-
C.
hasControlCab
Indicates that an entity is equipped with or includes a control cab used for operating or controlling it.
-
D.
controlSurfaces
Indicates that one entity functions as a control surface or set of control surfaces used to influence, steer, or regulate the behavior or state of another entity.
-
E.
hasArcades
Indicates that one entity features or contains arcaded structures (a series of arches or covered passageways) associated with another entity.
- F. None of above. chosen
Provenance (4 batches)
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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb145f96c8190a71bb9e442892e68 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb11bfd2c8190a805372589f73238 |
completed | March 7, 2026, 5:01 a.m. |
Created at: March 4, 2026, 7:34 p.m.