Triple
T32516448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Signal protocol Double Ratchet |
E831073
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cryptographic key management algorithm |
C59166
|
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: cryptographic key management algorithm Context triple: [Signal protocol Double Ratchet, instanceOf, cryptographic key management algorithm]
-
A.
cryptographic key management guideline
A cryptographic key management guideline is a set of policies and procedures that define how cryptographic keys are securely generated, distributed, stored, used, rotated, and destroyed throughout their lifecycle.
-
B.
cryptographic key
A cryptographic key is a piece of information, usually a string of bits, used by cryptographic algorithms to encrypt, decrypt, sign, or verify data securely.
-
C.
symmetric-key algorithm
A symmetric-key algorithm is a cryptographic method that uses the same secret key for both encryption and decryption of data.
-
D.
public-key cryptographic algorithm
A public-key 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, digital signatures, and key exchange over untrusted networks.
-
E.
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.
- F. None of above. chosen
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.