Triple
T29871258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintendo GameCube games on Wii |
E758599
|
entity |
| Predicate | controllerPortsUsed |
P138916
|
FINISHED |
| Object | GameCube controller ports on Wii |
—
|
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: GameCube controller ports on Wii | Statement: [Nintendo GameCube games on Wii, controllerPortsUsed, GameCube controller ports on Wii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controllerPortsUsed Context triple: [Nintendo GameCube games on Wii, controllerPortsUsed, GameCube controller ports on Wii]
-
A.
controllerPortCountUsed
chosen
Indicates the number of ports on a controller that are currently in use.
-
B.
controllerPortCount
Indicates the number of ports available on a given controller.
-
C.
controlledPort
Indicates that one entity has authority over or manages the operation or configuration of a specific port of another entity.
-
D.
executionPorts
Indicates a relationship where specific ports are used as the channels or endpoints through which an execution or process is carried out.
-
E.
connectionPort
Indicates a specific port through which two components, systems, or devices are connected or can communicate.
- F. None of above.
Provenance (3 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 29, 2026, 5:53 p.m.