Triple
T1892103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PlayStation 5 |
E41894
|
entity |
| Predicate | powerConsumptionMax |
P18504
|
FINISHED |
| Object | approximately 350 W |
—
|
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: approximately 350 W | Statement: [PlayStation 5, powerConsumptionMax, approximately 350 W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerConsumptionMax Context triple: [PlayStation 5, powerConsumptionMax, approximately 350 W]
-
A.
maximumPowerDuringOperation
chosen
Indicates the highest level of power that occurs while the system or component is operating.
-
B.
powerBudgetCharacteristic
Indicates a relationship where an entity’s power consumption limits, allocations, or constraints are specified as a characteristic or parameter.
-
C.
maximumPowerAtPSE
Indicates the highest level of power that can be delivered or drawn at the Power Sourcing Equipment (PSE) in the relationship.
-
D.
maxVoltage
Indicates the maximum electrical potential (voltage) that an entity can safely or normally handle, provide, or operate at.
-
E.
maximumPowerDeliveredToPD
Indicates the highest level of electrical power that can be supplied to the power-drawing device (PD) in this relationship.
- 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_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. |
Created at: March 4, 2026, 7:34 p.m.