Triple
T33392518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCSI over RDMA |
E855083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | remote direct memory access 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: remote direct memory access protocol Context triple: [SCSI over RDMA, instanceOf, remote direct memory access protocol]
-
A.
RDMA protocol
chosen
RDMA protocol is a high-performance networking technology that enables direct memory access between computers over a network, bypassing CPU involvement to reduce latency and increase throughput.
-
B.
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.
-
C.
remote execution protocol
A remote execution protocol is a standardized method that enables a client to securely request, manage, and monitor the execution of commands or programs on a remote system over a network.
-
D.
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.
-
E.
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.
- F. None of above.
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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:35 a.m.