Triple
T338727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ChaCha20 |
E6785
|
entity |
| Predicate | nonceSize |
P5657
|
FINISHED |
| Object | 96-bit |
—
|
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: 96-bit | Statement: [ChaCha20, nonceSize, 96-bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonceSize Context triple: [ChaCha20, nonceSize, 96-bit]
-
A.
consideredInsecureAtKeySize
Indicates that a cryptographic algorithm or mechanism is regarded as insecure when used with a specified key size.
-
B.
usesInitializationVectorLength
chosen
Indicates that an entity employs an initialization vector (IV) of a specified length in a cryptographic or security-related operation.
-
C.
supportsKeyLength
Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
-
D.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
E.
keyAgreement
Indicates that two or more parties participate in a cryptographic process to establish a shared secret key for secure communication.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae3a27c81909fc7deb600125fb1 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.