Triple
T11351334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RoCE |
E268845
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | RDMA protocol |
C30026
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: RDMA protocol Context triple: [RoCE, instanceOf, RDMA protocol]
-
A.
Fibre Channel protocol
Fibre Channel protocol is a high-speed network communication protocol primarily used to connect computer data storage to servers in storage area networks (SANs), providing reliable, lossless, and low-latency data transfer.
-
B.
InfiniBand interconnect generation
InfiniBand interconnect generation represents the process and configuration logic for creating, parameterizing, and managing high-speed InfiniBand fabric topologies and their associated connectivity resources.
-
C.
InfiniBand technology generation
InfiniBand technology generation represents a specific iteration of the InfiniBand architecture defined by its protocol features, performance capabilities, and compatibility characteristics across hardware and software implementations.
-
D.
NVMe protocol extension
An NVMe protocol extension is an enhancement to the base NVMe specification that introduces additional commands, features, or capabilities to improve performance, functionality, or interoperability of NVMe-based storage systems.
-
E.
InfiniBand link speed generation
InfiniBand link speed generation defines the classification and progression of InfiniBand interconnect data rates (e.g., SDR, DDR, QDR, FDR, EDR, HDR, NDR, XDR) across successive technology generations.
- F. None of above. chosen
Provenance (1 batch)
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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:33 p.m.