Triple
T28338308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST SP 800-108 |
E717740
|
entity |
| Predicate | KDFType |
P60768
|
FINISHED |
| Object | PRF-based KDF |
—
|
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: PRF-based KDF | Statement: [NIST SP 800-108, KDFType, PRF-based KDF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KDFType Context triple: [NIST SP 800-108, KDFType, PRF-based KDF]
-
A.
cryptographicType
Indicates the specific kind or category of cryptographic method, algorithm, or primitive associated with an entity or operation.
-
B.
keyDerivation
chosen
Indicates that one cryptographic key is generated or derived from another key or base secret using a specific derivation process.
-
C.
keyType
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
-
D.
modulusType
Indicates the type or category of modulus associated with an entity or operation (e.g., which modulus definition or scheme is being used).
-
E.
kernelType
Indicates the specific kind or category of kernel associated with or used by an entity.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64bd68ac08190b35887261657a408 |
completed | May 2, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:37 a.m.