Triple
T11351304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDMA |
E268844
|
entity |
| Predicate | transportProtocolFor |
P10376
|
FINISHED |
| Object | InfiniBand transport |
—
|
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: InfiniBand transport | Statement: [RDMA, transportProtocolFor, InfiniBand transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportProtocolFor Context triple: [RDMA, transportProtocolFor, InfiniBand transport]
-
A.
transportProtocol
chosen
Indicates the communication protocol used to transport data between entities in a networked interaction.
-
B.
targetProtocol
Indicates the communication protocol that an action, message, or connection is intended to use or be directed toward.
-
C.
targetsProtocol
Indicates that one entity is designed to interact with, affect, or be applied to a specific protocol.
-
D.
transportLayerFor
Indicates that one entity functions as the transport-layer protocol or mechanism used to carry or deliver another entity’s data.
-
E.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80148e2048190a716b515d78efdd1 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e6f8aeb4819080476f16a69b2ee3 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.