Triple
T31278935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA RTX A6000 |
E797606
|
entity |
| Predicate | maxPowerConsumption |
P18504
|
FINISHED |
| Object | 300 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: 300 W | Statement: [NVIDIA RTX A6000, maxPowerConsumption, 300 W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxPowerConsumption Context triple: [NVIDIA RTX A6000, maxPowerConsumption, 300 W]
-
A.
powerConsumptionWatts
Indicates the amount of electrical power an entity uses, measured in watts, during its operation.
-
B.
maximumPowerDuringOperation
chosen
Indicates the highest level of power that occurs while the system or component is operating.
-
C.
powerBudgetCharacteristic
Indicates a relationship where an entity’s power consumption limits, allocations, or constraints are specified as a characteristic or parameter.
-
D.
maximumPowerAtPSE
Indicates the highest level of power that can be delivered or drawn at the Power Sourcing Equipment (PSE) in the relationship.
-
E.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:13 p.m.