Triple
T31665911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA GeForce RTX 4080 |
E808123
|
entity |
| Predicate | supportsNVIDIAGSync |
P89364
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NVIDIA GeForce RTX 4080, supportsNVIDIAGSync, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNVIDIAGSync Context triple: [NVIDIA GeForce RTX 4080, supportsNVIDIAGSync, true]
-
A.
supportsIntelQuickSyncVideo
Indicates that one entity provides compatibility with or functional support for Intel Quick Sync Video hardware-accelerated video processing.
-
B.
supportsGraphicsSwitching
Indicates that an entity can dynamically switch between different graphics hardware or rendering modes, typically to balance performance and power usage.
-
C.
supportsGPUType
Indicates that one entity is compatible with, or capable of operating using, a specified type of GPU.
-
D.
supportsGPUBrand
chosen
Indicates that one entity is compatible with, or provides functional support for, a specified GPU brand.
-
E.
supportsExternalGPU
Indicates that an entity is capable of working with or providing connectivity for an external graphics processing unit (eGPU).
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:59 p.m.