Triple
T26408263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBC-MAC |
E663889
|
entity |
| Predicate | isNotSecureFor |
P6922
|
FINISHED |
| Object | variable-length messages without modifications |
—
|
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: variable-length messages without modifications | Statement: [CBC-MAC, isNotSecureFor, variable-length messages without modifications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotSecureFor Context triple: [CBC-MAC, isNotSecureFor, variable-length messages without modifications]
-
A.
isSecureFor
Indicates that one entity provides a level of protection or safety that makes it appropriate or safe for use, access, or interaction by another entity.
-
B.
consideredSecure
Indicates that something is regarded as safe from harm, risk, or unauthorized access according to given criteria or standards.
-
C.
insecureAbout
Indicates that one entity feels uncertain, self-doubting, or lacking confidence regarding some aspect of another entity or itself.
-
D.
hasSecurityConsideration
Indicates that there is a relevant security-related issue, risk, or precaution associated with the referenced entity.
-
E.
doesNotProtect
chosen
Indicates that an entity fails to provide protection or safeguarding to another entity or object.
- 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_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 26, 2026, 11:36 p.m.