Triple
T31750700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA GeForce RTX 4070 Ti |
E810406
|
entity |
| Predicate | recommendedPSUWatts |
P172964
|
FINISHED |
| Object | 700 |
—
|
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: 700 | Statement: [NVIDIA GeForce RTX 4070 Ti, recommendedPSUWatts, 700]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedPSUWatts Context triple: [NVIDIA GeForce RTX 4070 Ti, recommendedPSUWatts, 700]
-
A.
recommendedPsuWatts
chosen
Indicates the recommended power supply unit wattage needed to adequately support a given system or component configuration.
-
B.
recommendedPSU
Indicates that one entity is suggested or advised as the appropriate power supply unit (PSU) for another entity, typically based on compatibility or power requirements.
-
C.
powerAdapterWattage
Indicates the electrical power capacity, in watts, that a power adapter can supply.
-
D.
powerSupplyCapability
Indicates the ability of one entity to provide electrical power to another entity or system.
-
E.
powerConsumptionWatts
Indicates the amount of electrical power an entity uses, measured in watts, during its operation.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 30, 2026, 11:28 p.m.