Triple
T272131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diffie–Hellman key exchange |
E5655
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | key exchange protocol |
C994
|
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: key exchange protocol Context triple: [Diffie–Hellman key exchange, instanceOf, key exchange protocol]
-
A.
cryptographic protocol
chosen
A cryptographic protocol is a precisely defined sequence of operations and message exchanges that uses cryptographic primitives to achieve security goals such as confidentiality, integrity, authentication, and non-repudiation between parties.
-
B.
network security protocol
A network security protocol is a defined set of rules and procedures that protect data integrity, confidentiality, and authenticity during communication between devices over a network.
-
C.
communication protocol
A communication protocol is a defined set of rules and formats that enable reliable, structured exchange of data between two or more communicating entities in a networked system.
-
D.
communication protocol suite
A communication protocol suite is a coordinated set of network protocols that work together across different layers to enable reliable data exchange between devices in a communication system.
-
E.
network protocol
A network protocol is a standardized set of rules and formats that enable computers and devices to communicate and exchange data reliably over a network.
- 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.