Triple
T7934806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST SP 800-56B |
E184260
|
entity |
| Predicate | typeOfCryptography |
P21840
|
FINISHED |
| Object | asymmetric cryptography |
—
|
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: asymmetric cryptography | Statement: [NIST SP 800-56B, typeOfCryptography, asymmetric cryptography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCryptography Context triple: [NIST SP 800-56B, typeOfCryptography, asymmetric cryptography]
-
A.
cipherCategory
Indicates that one item is classified as a type or category of cipher to which the other item belongs.
-
B.
cryptographicModel
Indicates a relationship where one entity serves as, or is based on, a particular cryptographic scheme, framework, or formal model.
-
C.
algorithmType
chosen
Indicates the specific kind or category of algorithm associated with an entity or process.
-
D.
cryptographicRelevance
Indicates that something has significance, impact, or utility within a cryptographic context, such as for security, encryption, or cryptographic analysis.
-
E.
hasCrypt
Indicates that one entity possesses, contains, or is associated with a crypt belonging to or located within it.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aec394081909a9569c02ac372af |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.