Triple
T37149135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RDMA over Converged Ethernet |
E920316
|
entity |
| Predicate | RoCEv2DefaultUDPPort |
P187648
|
FINISHED |
| Object | 4791 |
—
|
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: 4791 | Statement: [RDMA over Converged Ethernet, RoCEv2DefaultUDPPort, 4791]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RoCEv2DefaultUDPPort Context triple: [RDMA over Converged Ethernet, RoCEv2DefaultUDPPort, 4791]
-
A.
RoCEv2Encapsulation
Indicates that data traffic is encapsulated using the RDMA over Converged Ethernet version 2 (RoCEv2) protocol for transport over an IP network.
-
B.
VLANIdentifierSizeBits
Indicates the number of bits used to represent a VLAN identifier in a networking context.
-
C.
portConfiguration
Indicates how ports are arranged, assigned, or set up for use within a system or device.
-
D.
dynamicPortRange
Indicates that a system or service uses a configurable range of network ports that can be dynamically allocated rather than fixed to a single port.
-
E.
portRange
Indicates the range of network ports over which a connection, service, or rule applies.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb78c982ac8190846efe8f6209e5d1 |
completed | May 6, 2026, 5:22 p.m. |
Created at: May 3, 2026, 4:15 p.m.