Triple
T37123854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HChaCha20 |
E919336
|
entity |
| Predicate | inputNonceSize |
P92328
|
FINISHED |
| Object | 128-bit nonce prefix |
—
|
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: 128-bit nonce prefix | Statement: [HChaCha20, inputNonceSize, 128-bit nonce prefix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputNonceSize Context triple: [HChaCha20, inputNonceSize, 128-bit nonce prefix]
-
A.
variantNonceSize
Indicates that there is a specific or differing size of nonce associated with a given variant in a cryptographic or protocol context.
-
B.
usesNonce
Indicates that one entity employs a nonce (a unique, typically one-time-use value) as part of its interaction or operation with another entity.
-
C.
nonceLength
chosen
Indicates the length or size of a nonce value used in a cryptographic or security-related context.
-
D.
requiresNonceUniqueness
Indicates that the action or process demands each nonce value be unique, preventing reuse across operations or transactions.
-
E.
isDeterministicWithFixedNonceAndKey
Indicates that the outcome of an operation is fully determined and repeatable when the same nonce and key are used, with no additional randomness involved.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.