Triple

T21191268
Position Surface form Disambiguated ID Type / Status
Subject IKEv1 E522215 entity
Predicate vulnerabilities P56378 FINISHED
Object susceptible to certain denial-of-service attacks 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: susceptible to certain denial-of-service attacks | Statement: [IKEv1, vulnerabilities, susceptible to certain denial-of-service attacks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: vulnerabilities
Context triple: [IKEv1, vulnerabilities, susceptible to certain denial-of-service attacks]
  • A. vulnerabilityType chosen
    Indicates the specific kind or category of vulnerability associated with an entity or situation.
  • B. strategicVulnerability
    Indicates a relationship where an entity is exposed to potential harm or disadvantage in a way that can be deliberately exploited within a strategic or competitive context.
  • C. vulnerabilitySource
    Indicates that one entity is the origin, cause, or contributing factor of another entity’s vulnerability or weakness.
  • D. exploits
    Indicates that one entity unfairly or selfishly uses another entity or resource for its own advantage or benefit.
  • E. securityAdvisory
    Indicates a relationship where an entity issues, references, or is associated with a warning or guidance about security vulnerabilities, risks, or protective measures.
  • 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_69e0b51061388190aa03f19700d3ef04 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e733381f288190b3da795f62a39568 completed April 21, 2026, 8:20 a.m.
PD Predicate disambiguation batch_69e5f6027c248190a170a36612bd337e completed April 20, 2026, 9:46 a.m.
Created at: April 16, 2026, 3:07 p.m.