Triple
T25521355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST SP 800-38E |
E639658
|
entity |
| Predicate | usesBlockCipher |
P92332
|
FINISHED |
| Object | AES |
—
|
NE NERFINISHED |
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: AES | Statement: [NIST SP 800-38E, usesBlockCipher, AES]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBlockCipher Context triple: [NIST SP 800-38E, usesBlockCipher, AES]
-
A.
requiresBlockCipher
chosen
Indicates that performing this operation or protocol depends on the use of a block cipher as its underlying cryptographic primitive.
-
B.
blockCipherMode
Indicates the specific operational mode used by a block cipher to process data (e.g., how blocks are chained, padded, or transformed during encryption/decryption).
-
C.
usesSBoxes
Indicates that one entity employs substitution boxes (S-boxes) as part of its operation or implementation.
-
D.
usesKeyDependentSBoxes
Indicates that the cryptographic construction employs S-boxes whose behavior or mapping depends on the value of the secret key.
-
E.
usesFeistelStructure
Indicates that one entity employs a Feistel network structure as the core design of its cryptographic or transformation process.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 3 p.m.