Triple
T31750714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA GeForce RTX 4070 Ti |
E810406
|
entity |
| Predicate | supportsNVIDIALink |
P207510
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [NVIDIA GeForce RTX 4070 Ti, supportsNVIDIALink, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNVIDIALink Context triple: [NVIDIA GeForce RTX 4070 Ti, supportsNVIDIALink, false]
-
A.
supportsOculusLink
Indicates that one entity is compatible with and can operate using the Oculus Link connection feature provided by another entity.
-
B.
hasLinkCableSupport
Indicates that one entity supports being connected to another via a link cable for interaction or data exchange.
-
C.
supportsGPUBrand
Indicates that one entity is compatible with, or provides functional support for, a specified GPU brand.
-
D.
supportsPCConnectivity
Indicates that one entity enables or is compatible with connection or communication to a personal computer.
-
E.
supportsGPUType
Indicates that one entity is compatible with, or capable of operating using, a specified type of GPU.
- F. None of above. chosen
Provenance (4 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_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 11:28 p.m.