Triple
T32550421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIGMA key exchange protocol |
E831957
|
entity |
| Predicate | addressesWeaknessOf |
P3847
|
FINISHED |
| Object | naive signed Diffie–Hellman |
—
|
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: naive signed Diffie–Hellman | Statement: [SIGMA key exchange protocol, addressesWeaknessOf, naive signed Diffie–Hellman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressesWeaknessOf Context triple: [SIGMA key exchange protocol, addressesWeaknessOf, naive signed Diffie–Hellman]
-
A.
hasWeakness
Indicates that one entity is vulnerable to, or can be adversely affected or defeated by, another entity.
-
B.
addressesIssue
chosen
Indicates that one entity deals with, responds to, or attempts to resolve a specific issue associated with another entity.
-
C.
typeOfSecurityAddressed
Indicates the category or kind of security concern, risk, or protection that is being addressed in a given context.
-
D.
riskAddressed
Indicates that a particular risk has been identified and is being mitigated, managed, or otherwise handled by an associated action, control, or measure.
-
E.
strategicVulnerability
Indicates a relationship where an entity is exposed to potential harm or disadvantage in a way that can be deliberately exploited within a strategic or competitive context.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:02 a.m.