Triple
T10682053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AEAD_CHACHA20_POLY1305 |
E251780
|
entity |
| Predicate | usesKeyDerivation |
P60768
|
FINISHED |
| Object | ChaCha20 block function for Poly1305 key |
—
|
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: ChaCha20 block function for Poly1305 key | Statement: [AEAD_CHACHA20_POLY1305, usesKeyDerivation, ChaCha20 block function for Poly1305 key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesKeyDerivation Context triple: [AEAD_CHACHA20_POLY1305, usesKeyDerivation, ChaCha20 block function for Poly1305 key]
-
A.
keyDerivation
chosen
Indicates that one cryptographic key is generated or derived from another key or base secret using a specific derivation process.
-
B.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
C.
keyUse
Indicates that one entity is used as a key or means of access, control, or identification for another entity.
-
D.
hasKeyAgreement
Indicates that two parties share or have established a cryptographic key agreement used to securely derive a common secret key.
-
E.
canBeEncryptedUsing
Indicates that one entity is capable of being transformed into a secure, encoded form by applying the encryption method or key represented by another entity.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc30be481909922844b539b622d |
completed | April 9, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:10 p.m.