Triple
T11327248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XChaCha20-Poly1305 AEAD construction |
E268251
|
entity |
| Predicate | nonceMisuseResistance |
P98522
|
FINISHED |
| Object | improved but not fully misuse-resistant |
—
|
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: improved but not fully misuse-resistant | Statement: [XChaCha20-Poly1305 AEAD construction, nonceMisuseResistance, improved but not fully misuse-resistant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonceMisuseResistance Context triple: [XChaCha20-Poly1305 AEAD construction, nonceMisuseResistance, improved but not fully misuse-resistant]
-
A.
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.
-
B.
nonceRequirement
Indicates that a unique, one-time-use value (nonce) is required to be present or validated as part of the interaction or transaction between entities.
-
C.
nonceLength
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.
requiresKeyAndNonceUniqueness
Indicates that the operation or protocol demands both a unique key and a unique nonce for each use or session to ensure security.
- F. None of above. chosen
Provenance (4 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e2253881909518cad0f12ef612 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796d049e88190a9fd7508f477f541 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:32 p.m.