Triple
T28397127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS DHE ciphersuites |
E719310
|
entity |
| Predicate | relatedAttack |
P201468
|
FINISHED |
| Object | Logjam attack |
—
|
NE NERFINISHED |
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: Logjam attack | Statement: [TLS DHE ciphersuites, relatedAttack, Logjam attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedAttack Context triple: [TLS DHE ciphersuites, relatedAttack, Logjam attack]
-
A.
knownAttacks
Indicates that one entity is aware of, or has information about, specific attacks associated with another entity.
-
B.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
C.
coordinatedAttacksAlsoTargeted
Indicates that in a set of coordinated attacks, the same target was also attacked as part of those coordinated actions.
-
D.
oftenAttackedBy
Indicates that an entity is frequently the target of attacks carried out by another entity.
-
E.
attacks
Indicates that one entity initiates an aggressive or harmful action directed toward 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fff9b126b4819085a4cf8791d388d1 |
completed | May 10, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69fff8f913a881908d3b7e490d92631f |
completed | May 10, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fff9b0338c8190a24ed0b5dc9784b2 |
completed | May 10, 2026, 3:21 a.m. |
Created at: April 28, 2026, 1:17 a.m.