Triple
T26408262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBC-MAC |
E663889
|
entity |
| Predicate | isSecureFor |
P160598
|
FINISHED |
| Object | fixed-length messages |
—
|
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: fixed-length messages | Statement: [CBC-MAC, isSecureFor, fixed-length messages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSecureFor Context triple: [CBC-MAC, isSecureFor, fixed-length messages]
-
A.
consideredSecure
Indicates that something is regarded as safe from harm, risk, or unauthorized access according to given criteria or standards.
-
B.
securedAgainst
Indicates that one entity is protected or safeguarded against threats, risks, or harmful actions originating from another entity or source.
-
C.
isSecureFacility
Indicates that a facility has protections, controls, and safeguards in place to prevent unauthorized access, tampering, or security breaches.
-
D.
securedVia
Indicates that something is protected, authenticated, or made safe through a specified method, mechanism, or channel.
-
E.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
- 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_69f610faa77081908956b6e8b5b1570c |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 26, 2026, 11:36 p.m.