Triple
T31831704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA GeForce RTX 4070 |
E812554
|
entity |
| Predicate | recommendedPsu |
P172964
|
FINISHED |
| Object | 650 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: 650 W | Statement: [NVIDIA GeForce RTX 4070, recommendedPsu, 650 W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedPsu Context triple: [NVIDIA GeForce RTX 4070, recommendedPsu, 650 W]
-
A.
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.
-
B.
recommendedPsuWatts
chosen
Indicates the recommended power supply unit wattage needed to adequately support a given system or component configuration.
-
C.
isPSU
Indicates that one entity functions as the power supply unit (PSU) for another entity.
-
D.
powerSupplyCapability
Indicates the ability of one entity to provide electrical power to another entity or system.
-
E.
powerSupplyInterface
Indicates a relationship where one entity provides or connects an electrical power source to another entity through a defined interface.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 30, 2026, 11:47 p.m.