Triple
T33027222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cipher Block Chaining |
E845073
|
entity |
| Predicate | firstBlockDecryptionUses |
P79867
|
FINISHED |
| Object | initialization vector |
—
|
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: initialization vector | Statement: [Cipher Block Chaining, firstBlockDecryptionUses, initialization vector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstBlockDecryptionUses Context triple: [Cipher Block Chaining, firstBlockDecryptionUses, initialization vector]
-
A.
decryptionRequires
chosen
Indicates that performing decryption of some data depends on or needs a specified key, resource, or condition to be fulfilled.
-
B.
requiresBlockCipher
Indicates that performing this operation or protocol depends on the use of a block cipher as its underlying cryptographic primitive.
-
C.
initialBlock
Indicates that something serves as the first or starting block in a sequence, structure, or process.
-
D.
decryptionComplexity
Indicates the level of computational effort or difficulty required to decrypt data protected by a given cryptographic method or key.
-
E.
usesInitialPermutation
Indicates that an operation or process applies an initial permutation step to its input elements before performing further actions.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:23 a.m.