Triple
T1712029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DNSSEC |
E37203
|
entity |
| Predicate | mitigates |
P9925
|
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, mitigates, DNS cache poisoning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mitigates Context triple: [DNSSEC, mitigates, DNS cache poisoning]
-
A.
reduces
chosen
Indicates that one entity causes a decrease in the amount, intensity, degree, or impact of another entity.
-
B.
negates
Indicates that one entity denies, contradicts, or renders false the assertion, state, or effect expressed by another.
-
C.
remedy
Indicates that one entity serves to cure, alleviate, or counteract a problem, illness, or undesirable condition affecting another entity.
-
D.
relievedBy
Indicates that one entity eases, reduces, or removes the burden, pain, stress, or responsibility experienced by another entity.
-
E.
neutralized
Indicates that one entity has rendered another entity ineffective, harmless, or no longer able to exert its intended effect.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab7521878c8190b9e7739b8c3fc705 |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61bd46d48190915500d75a9d8e94 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.