Triple
T32516398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Signal protocol X3DH |
E831072
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | asynchronous key exchange protocol |
C53997
|
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: asynchronous key exchange protocol Context triple: [Signal protocol X3DH, instanceOf, asynchronous key exchange protocol]
-
A.
cryptographic protocol component
chosen
A cryptographic protocol component is a modular element—such as a key exchange, authentication step, or encryption mechanism—that participates in a larger protocol to provide specific security properties like confidentiality, integrity, or authenticity.
-
B.
cryptographic protocol framework
A cryptographic protocol framework is a structured set of tools, abstractions, and rules that enables the design, specification, analysis, and implementation of secure communication protocols.
-
C.
asymmetric cryptographic algorithm
An asymmetric cryptographic algorithm is a method that uses a mathematically related pair of keys—one public and one private—to enable secure operations such as encryption, decryption, and digital signatures without sharing secret keys.
-
D.
cryptographic protocol
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.
-
E.
IPsec key exchange phase
IPsec key exchange phase is the process in which two network entities securely negotiate and establish shared cryptographic keys and security parameters used to protect subsequent IPsec communications.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1 a.m.