Triple
T21191538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST SP 800-67 |
E522221
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | NIST Cryptographic Module Validation Program |
—
|
NE NERFINISHED |
How this triple was built (3 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: NIST Cryptographic Module Validation Program | Statement: [NIST SP 800-67, relatedTo, NIST Cryptographic Module Validation Program]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NIST Cryptographic Module Validation Program Context triple: [NIST SP 800-67, relatedTo, NIST Cryptographic Module Validation Program]
-
A.
NIST cryptographic standards framework
The NIST cryptographic standards framework is a comprehensive set of guidelines and specifications developed by the U.S. National Institute of Standards and Technology to ensure secure, interoperable, and reliable cryptographic mechanisms for federal and industry use.
-
B.
NIST SP 800-38C
NIST SP 800-38C is a NIST Special Publication that specifies the CCM (Counter with CBC-MAC) mode of operation for block cipher encryption used to provide both confidentiality and integrity.
-
C.
NIST SP 800-56C
NIST SP 800-56C is a NIST Special Publication that provides recommendations for key derivation methods in key-establishment schemes used in cryptographic systems.
-
D.
NIST SP 800-38D
NIST SP 800-38D is a NIST special publication that specifies the Galois/Counter Mode (GCM) of operation for the Advanced Encryption Standard (AES) and provides guidelines for its secure use.
-
E.
NIST SP 800-38E
NIST SP 800-38E is a NIST Special Publication that specifies the XTS-AES mode of operation for the Advanced Encryption Standard, primarily for encrypting data on storage devices.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: NIST Cryptographic Module Validation Program Target entity description: The NIST Cryptographic Module Validation Program is a U.S. government program that tests and certifies cryptographic modules for compliance with federal security standards such as FIPS 140.
-
A.
NIST cryptographic standards framework
The NIST cryptographic standards framework is a comprehensive set of guidelines and specifications developed by the U.S. National Institute of Standards and Technology to ensure secure, interoperable, and reliable cryptographic mechanisms for federal and industry use.
-
B.
NIST SP 800-38C
NIST SP 800-38C is a NIST Special Publication that specifies the CCM (Counter with CBC-MAC) mode of operation for block cipher encryption used to provide both confidentiality and integrity.
-
C.
NIST SP 800-56C
NIST SP 800-56C is a NIST Special Publication that provides recommendations for key derivation methods in key-establishment schemes used in cryptographic systems.
-
D.
NIST SP 800-38D
NIST SP 800-38D is a NIST special publication that specifies the Galois/Counter Mode (GCM) of operation for the Advanced Encryption Standard (AES) and provides guidelines for its secure use.
-
E.
NIST SP 800-38E
NIST SP 800-38E is a NIST Special Publication that specifies the XTS-AES mode of operation for the Advanced Encryption Standard, primarily for encrypting data on storage devices.
- F. None of above. chosen
Provenance (2 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733381f288190b3da795f62a39568 |
completed | April 21, 2026, 8:20 a.m. |
Created at: April 16, 2026, 3:07 p.m.