Triple
T26408538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST |
E663895
|
entity |
| Predicate | selectedCipher |
P161005
|
FINISHED |
| Object | Rijndael |
—
|
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: Rijndael | Statement: [NIST, selectedCipher, Rijndael]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectedCipher Context triple: [NIST, selectedCipher, Rijndael]
-
A.
cipherCategory
Indicates that one item is classified as a type or category of cipher to which the other item belongs.
-
B.
standardizedCipher
chosen
Indicates that an encryption method or cipher conforms to an established, widely accepted standard or specification.
-
C.
cipherKey
Indicates that one entity serves as the cryptographic key used to encrypt or decrypt information associated with another entity.
-
D.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
E.
cryptographicType
Indicates the specific kind or category of cryptographic method, algorithm, or primitive associated with an entity or operation.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 26, 2026, 11:36 p.m.