Triple
T26408283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBC-MAC |
E663889
|
entity |
| Predicate | requiresBlockSize |
P180121
|
FINISHED |
| Object | block size of underlying 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 size of underlying cipher | Statement: [CBC-MAC, requiresBlockSize, block size of underlying cipher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresBlockSize Context triple: [CBC-MAC, requiresBlockSize, block size of underlying cipher]
-
A.
requiresBlockCipher
Indicates that performing this operation or protocol depends on the use of a block cipher as its underlying cryptographic primitive.
-
B.
blockSize
Indicates the size or capacity of a discrete block unit within a larger structure or system.
-
C.
supportedBlockSizes
Indicates the specific block sizes that an entity is capable of handling or operating with.
-
D.
usesAllocationBlockSize
Indicates that one entity operates with or depends on a specific allocation block size defined or provided by another entity.
-
E.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f73221eef88190bd8905e6e9f5a586 |
completed | May 3, 2026, 11:31 a.m. |
Created at: April 26, 2026, 11:36 p.m.