Triple
T26409195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCM |
E663912
|
entity |
| Predicate | MACMode |
P95290
|
FINISHED |
| Object | CBC-MAC over 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: CBC-MAC over block cipher | Statement: [CCM, MACMode, CBC-MAC over block cipher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MACMode Context triple: [CCM, MACMode, CBC-MAC over block cipher]
-
A.
MACType
chosen
Indicates the type or category of a Medium Access Control (MAC) mechanism or protocol used in a communication system.
-
B.
blockCipherMode
Indicates the specific operational mode used by a block cipher to process data (e.g., how blocks are chained, padded, or transformed during encryption/decryption).
-
C.
signalingMode
Indicates the method or mechanism by which one entity communicates or transmits signals to another.
-
D.
modeADescription
Indicates the descriptive text or explanation associated with a particular mode of operation or state.
-
E.
modeType
Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
- 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.