Triple
T31278956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA RTX A6000 |
E797606
|
entity |
| Predicate | supportsNvidiaOmniverse |
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 RTX A6000, supportsNvidiaOmniverse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNvidiaOmniverse Context triple: [NVIDIA RTX A6000, supportsNvidiaOmniverse, true]
-
A.
supportsOculusLink
Indicates that one entity is compatible with and can operate using the Oculus Link connection feature provided by another entity.
-
B.
supportsGPUBrand
chosen
Indicates that one entity is compatible with, or provides functional support for, a specified GPU brand.
-
C.
supportsOrchestrator
Indicates that one entity provides the necessary capabilities or compatibility for another entity to function as an orchestrator within a coordinated system or workflow.
-
D.
supportsVendor
Indicates that one entity provides assistance, resources, or endorsement to a vendor in carrying out its activities or services.
-
E.
supportsPCVRConnection
Indicates that an entity enables or is compatible with establishing a PC-based virtual reality (VR) connection.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:13 p.m.