Triple
T8815081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WiiConnect24 |
E209756
|
entity |
| Predicate | powerConsumptionConcern |
P34611
|
FINISHED |
| Object | higher standby power usage |
—
|
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: higher standby power usage | Statement: [WiiConnect24, powerConsumptionConcern, higher standby power usage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerConsumptionConcern Context triple: [WiiConnect24, powerConsumptionConcern, higher standby power usage]
-
A.
energyUse
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
B.
energyUtilization
Indicates how effectively an entity uses available energy to perform work or sustain its functions.
-
C.
powerOptimizationFor
Indicates a relationship where one entity is used to improve, manage, or optimize the power consumption or power efficiency of another entity.
-
D.
showsPowerUse
Indicates that one entity demonstrates or exercises power, influence, or control over another entity or within a given context.
-
E.
electricityUse
chosen
Indicates the amount or pattern of electrical energy consumed by an entity during a specified period or activity.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff2ff248190bafcafe8b3860e53 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.