Triple
T11327217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XChaCha20-Poly1305 AEAD construction |
E268251
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | authenticated encryption with associated data scheme |
C16295
|
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: authenticated encryption with associated data scheme Context triple: [XChaCha20-Poly1305 AEAD construction, instanceOf, authenticated encryption with associated data scheme]
-
A.
cryptographic data structure
chosen
A cryptographic data structure is a data organization that uses cryptographic primitives to ensure properties like integrity, authenticity, privacy, or verifiability of the stored or processed information.
-
B.
stream cipher evaluation initiative
A stream cipher evaluation initiative is a coordinated effort to systematically analyze, compare, and validate the security, performance, and practicality of stream cipher algorithms against defined criteria and real-world use cases.
-
C.
encryption scheme
An encryption scheme is a systematic method that transforms readable data into an unreadable form using algorithms and keys to ensure confidentiality, integrity, and secure communication.
-
D.
symmetric-key algorithm
A symmetric-key algorithm is a cryptographic method that uses the same secret key for both encryption and decryption of data.
-
E.
block cipher mode of operation
A block cipher mode of operation is a method that specifies how to repeatedly apply a block cipher’s fixed-size transformation to larger or variably sized data to achieve secure encryption and decryption.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:32 p.m.