Triple
T9026602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game Boy Player |
E216060
|
entity |
| Predicate | powerSuppliedBy |
P11313
|
FINISHED |
| Object | Nintendo GameCube power supply |
—
|
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: Nintendo GameCube power supply | Statement: [Game Boy Player, powerSuppliedBy, Nintendo GameCube power supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerSuppliedBy Context triple: [Game Boy Player, powerSuppliedBy, Nintendo GameCube power supply]
-
A.
supplyVoltageType
Indicates the type or category of supply voltage associated with or required by an entity.
-
B.
hasPowerSupplyType
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
-
C.
suppliesPowerTo
chosen
Indicates that one entity provides electrical or energy power required for the operation or functioning of another entity.
-
D.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
E.
powerAdapterWattage
Indicates the electrical power capacity, in watts, that a power adapter can supply.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7eb5b881908ace0c3327f06161 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.