Triple
T26409151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GHASH |
E663911
|
entity |
| Predicate | subkeyDerivation |
P60607
|
FINISHED |
| Object | derived from block cipher key in GCM |
—
|
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: derived from block cipher key in GCM | Statement: [GHASH, subkeyDerivation, derived from block cipher key in GCM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subkeyDerivation Context triple: [GHASH, subkeyDerivation, derived from block cipher key in GCM]
-
A.
keyDerivation
Indicates that one cryptographic key is generated or derived from another key or base secret using a specific derivation process.
-
B.
nonceDerivation
Indicates the process or method by which a nonce value is generated or derived from given inputs or parameters.
-
C.
keyExpansion
chosen
Indicates the process of deriving a set of subkeys from an original key for use in a cryptographic algorithm.
-
D.
usesKeyDependentSBoxes
Indicates that the cryptographic construction employs S-boxes whose behavior or mapping depends on the value of the secret key.
-
E.
canDerive
Indicates that one entity can be logically or procedurally obtained, inferred, or produced from another entity based on defined rules or transformations.
- 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_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:37 p.m.