Triple

T54100
Position Surface form Disambiguated ID Type / Status
Subject Domain Name System E1065 entity
Predicate vulnerability P583 FINISHED
Object 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: cache poisoning | Statement: [Domain Name System, vulnerability, cache poisoning]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: vulnerability
Context triple: [Domain Name System, vulnerability, cache poisoning]
  • A. susceptibleTo chosen
    Indicates that one entity is vulnerable or likely to be affected, harmed, or influenced by another entity or factor.
  • B. security
    Indicates that an entity provides protection, safety measures, or safeguards to another entity or against specific threats or risks.
  • C. fault
    Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
  • D. securityFeature
    Indicates that an entity provides, embodies, or is associated with a mechanism or property intended to enhance safety, protection, or defense against threats or vulnerabilities.
  • E. securityProgram
    Indicates that an entity is associated with, participates in, or is governed by a security program, such as a set of policies, controls, or initiatives related to safety or protection.
  • 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_69a248adc5b48190aa8db9fb092fb28a completed Feb. 28, 2026, 1:45 a.m.
NER Named-entity recognition batch_69a24b3a9e848190b80de3c858678b3a completed Feb. 28, 2026, 1:56 a.m.
PD Predicate disambiguation batch_69a24ac52fb08190aa7c38f83434f795 completed Feb. 28, 2026, 1:54 a.m.
Created at: Feb. 28, 2026, 1:50 a.m.