Triple
T10157726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AES-CCM |
E233814
|
entity |
| Predicate | usesModeForConfidentiality |
P92327
|
FINISHED |
| Object | CTR |
—
|
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: CTR | Statement: [AES-CCM, usesModeForConfidentiality, CTR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesModeForConfidentiality Context triple: [AES-CCM, usesModeForConfidentiality, CTR]
-
A.
hasConfidentialityObligation
Indicates that an entity is bound by a duty to keep certain information secret and not disclose it to unauthorized parties.
-
B.
confidentialityProtectedBy
Indicates that the confidentiality of some information is safeguarded or ensured by a specified protection mechanism, policy, or entity.
-
C.
hasProtectionPurpose
Indicates that something is intended or designed to serve a protective function or goal.
-
D.
usesModality
Indicates that an action, communication, or process is carried out through or characterized by a particular modality (such as visual, auditory, tactile, or another mode of expression or operation).
-
E.
requiresEncryption
Indicates that one entity must use encryption when communicating with, storing data for, or otherwise interacting with 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5507f08190b47f797bacd5640c |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8f869c8190a82ad040993e0244 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9:09 p.m.