Triple
T1907790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNSSEC ZSK |
E38040
|
entity |
| Predicate | threatMitigated |
P19863
|
FINISHED |
| Object | DNS cache poisoning |
—
|
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: DNS cache poisoning | Statement: [DNSSEC ZSK, threatMitigated, DNS cache poisoning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatMitigated Context triple: [DNSSEC ZSK, threatMitigated, DNS cache poisoning]
-
A.
threatTypeAddressed
chosen
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
-
B.
threatStatus
Indicates the level or category of risk or danger posed by one entity to another or to a defined system or environment.
-
C.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
D.
threatTypeEngaged
Indicates that an entity has actively engaged with or responded to a specific type of threat.
-
E.
threat
Indicates a relationship where one entity expresses or poses potential harm, danger, or negative consequences toward another entity.
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafeba3d88190afcce67483d8625b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.