Triple
T26408418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serpent cipher |
E663892
|
entity |
| Predicate | roundKeyGeneration |
P60607
|
FINISHED |
| Object | key schedule |
—
|
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: key schedule | Statement: [Serpent cipher, roundKeyGeneration, key schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundKeyGeneration Context triple: [Serpent cipher, roundKeyGeneration, key schedule]
-
A.
keyExpansion
chosen
Indicates the process of deriving a set of subkeys from an original key for use in a cryptographic algorithm.
-
B.
usesKeyScheduleLike
Indicates that one cryptographic algorithm employs a key schedule that is the same as, or closely derived from, the key schedule of another algorithm.
-
C.
cipherKey
Indicates that one entity serves as the cryptographic key used to encrypt or decrypt information associated with another entity.
-
D.
keyDerivation
Indicates that one cryptographic key is generated or derived from another key or base secret using a specific derivation process.
-
E.
roundsFor128BitKey
Indicates the number of algorithmic rounds required when operating with a 128-bit cryptographic key.
- 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_69f610faa77081908956b6e8b5b1570c |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 11:36 p.m.