Triple
T7414684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCMP |
E171099
|
entity |
| Predicate | cipherSuiteIdentifier |
P76795
|
FINISHED |
| Object | CCMP-128 |
—
|
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: CCMP-128 | Statement: [CCMP, cipherSuiteIdentifier, CCMP-128]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cipherSuiteIdentifier Context triple: [CCMP, cipherSuiteIdentifier, CCMP-128]
-
A.
supportsCipherSuite
Indicates that one entity is capable of using or handling a specified cryptographic cipher suite in secure communications.
-
B.
securityModelIdentifier
Indicates the specific security model or framework under which an entity, interaction, or policy is defined or governed.
-
C.
cipherKey
Indicates that one entity serves as the cryptographic key used to encrypt or decrypt information associated with another entity.
-
D.
keyAgreement
Indicates that two or more parties participate in a cryptographic process to establish a shared secret key for secure communication.
-
E.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c509ac8190876f207267a33a3b |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1c3307481909a7f6bb69d4fddac |
completed | March 27, 2026, 9:08 p.m. |
Created at: March 27, 2026, 3:11 p.m.