Triple
T31278931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NVIDIA RTX A6000 |
E797606
|
entity |
| Predicate | nvlinkBridgeWidth |
P171536
|
FINISHED |
| Object | 112.5 GB/s per direction |
—
|
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: 112.5 GB/s per direction | Statement: [NVIDIA RTX A6000, nvlinkBridgeWidth, 112.5 GB/s per direction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nvlinkBridgeWidth Context triple: [NVIDIA RTX A6000, nvlinkBridgeWidth, 112.5 GB/s per direction]
-
A.
supportsLinkWidth
Indicates that one entity is capable of accommodating or enabling a specified width for a link or connection between components.
-
B.
maxPCIeLanesPerSocket
Indicates the maximum number of PCIe lanes that a single processor socket can support.
-
C.
bridgeName
Indicates the designated name assigned to a specific bridge.
-
D.
hasBridgeLayer
Indicates that one entity includes or is associated with a specific bridge layer within its structure or configuration.
-
E.
bridgeLength
Indicates the physical length or span of a bridge structure.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 29, 2026, 9:13 p.m.