Triple
T26408255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBC-MAC |
E663889
|
entity |
| Predicate | usesCipherType |
P135207
|
FINISHED |
| Object | block cipher |
—
|
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: block cipher | Statement: [CBC-MAC, usesCipherType, block cipher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCipherType Context triple: [CBC-MAC, usesCipherType, block cipher]
-
A.
ciphertextType
Indicates the specific kind or format of ciphertext produced or used in an encryption process.
-
B.
cryptographicType
chosen
Indicates the specific kind or category of cryptographic method, algorithm, or primitive associated with an entity or operation.
-
C.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
D.
canBeEncryptedUsing
Indicates that one entity is capable of being transformed into a secure, encoded form by applying the encryption method or key represented by another entity.
-
E.
cryptUse
Indicates that one entity uses, applies, or relies on a cryptographic method, key, or mechanism in relation to another entity or data.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 26, 2026, 11:36 p.m.