Triple
T18553284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragonfly key exchange |
E453435
|
entity |
| Predicate | hasThreatModel |
P132137
|
FINISHED |
| Object | adversary with access to protocol transcripts |
—
|
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: adversary with access to protocol transcripts | Statement: [Dragonfly key exchange, hasThreatModel, adversary with access to protocol transcripts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThreatModel Context triple: [Dragonfly key exchange, hasThreatModel, adversary with access to protocol transcripts]
-
A.
hasThreats
Indicates that one entity poses or is associated with potential danger, harm, or adverse consequences toward another entity.
-
B.
recognizesThreat
Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
-
C.
hasSecurityArchitecture
Indicates that an entity is associated with or defined by a particular security architecture design or framework.
-
D.
hasSecurityNotion
Indicates that one entity possesses, defines, or is associated with a particular concept or notion of security in relation to another entity or context.
-
E.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e538027b94819082a4c4af66e170d7 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:38 a.m.