Triple
T31632329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA GeForce RTX 4090 |
E807201
|
entity |
| Predicate | tgpWatts |
P89369
|
FINISHED |
| Object | 450 |
—
|
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: 450 | Statement: [NVIDIA GeForce RTX 4090, tgpWatts, 450]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tgpWatts Context triple: [NVIDIA GeForce RTX 4090, tgpWatts, 450]
-
A.
powerConsumptionWatts
Indicates the amount of electrical power an entity uses, measured in watts, during its operation.
-
B.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
C.
typicalPower
chosen
Indicates the usual or characteristic amount of power associated with an entity under normal operating conditions.
-
D.
powerOutputApprox
Indicates an approximate or estimated value for the power output produced by an entity or system.
-
E.
intendedPower
Indicates the level or amount of power that an entity is designed, planned, or expected to produce, use, or deliver under intended operating conditions.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8e631d88190aa2d39f7f485c1b8 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:45 p.m.