Triple
T11351301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDMA |
E268844
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | RoCE |
E268845
|
NE 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: RoCE | Statement: [RDMA, hasVariant, RoCE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RoCE Context triple: [RDMA, hasVariant, RoCE]
-
A.
RoCE
chosen
RoCE (RDMA over Converged Ethernet) is a network protocol that enables high-throughput, low-latency remote direct memory access over Ethernet networks, commonly used in data centers and storage systems.
-
B.
InfiniBand
InfiniBand is a high-speed, low-latency communications standard commonly used as the interconnect fabric in supercomputers and large-scale data centers.
-
C.
RDMA
RDMA (Remote Direct Memory Access) is a high-performance networking technology that allows one computer to directly access the memory of another without involving the operating system or CPU, significantly reducing latency and CPU overhead in data transfers.
-
D.
iWARP
iWARP is a network protocol suite that enables RDMA (Remote Direct Memory Access) over standard TCP/IP networks to provide low-latency, high-throughput data transfer.
-
E.
IEEE 802.1Qfv
IEEE 802.1Qfv is an amendment to the IEEE 802.1Q standard that defines enhancements for flexible queuing and forwarding behaviors in bridged and virtualized Ethernet networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea24489081908fbf47fd2e6d709c |
completed | April 9, 2026, 6:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5439a7ee481908d244f79041b3af6 |
completed | April 19, 2026, 9:05 p.m. |
Created at: April 8, 2026, 9:33 p.m.