Triple
T1893444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DLSS |
E41923
|
entity |
| Predicate | hardwareRequirement |
P29568
|
FINISHED |
| Object | NVIDIA RTX graphics card |
—
|
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: NVIDIA RTX graphics card | Statement: [DLSS, hardwareRequirement, NVIDIA RTX graphics card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardwareRequirement Context triple: [DLSS, hardwareRequirement, NVIDIA RTX graphics card]
-
A.
platformRequirement
chosen
Indicates that one entity specifies a necessary platform or environment condition that must be met for another entity to function or be applicable.
-
B.
hostRequirement
Indicates that one entity specifies or imposes necessary conditions or resources that another entity (the host) must provide or satisfy.
-
C.
requiresSoftware
Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
-
D.
hardwareUsedBy
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
-
E.
hardwareRole
Indicates the functional role or purpose that a piece of hardware serves within a system or configuration.
- 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_69abb1497df08190ad90dd89f76208ca |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe7e7e88190b58c0df59187c0c2 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.