Triple

T12608115
Position Surface form Disambiguated ID Type / Status
Subject Ababeel missile E301035 entity
Predicate designedToTarget P61966 FINISHED
Object regional adversary strategic targets 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: regional adversary strategic targets | Statement: [Ababeel missile, designedToTarget, regional adversary strategic targets]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedToTarget
Context triple: [Ababeel missile, designedToTarget, regional adversary strategic targets]
  • A. usesTarget
    Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
  • B. isDesignedFor
    Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
  • C. targetedDevice
    Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
  • D. intendedTargets chosen
    Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
  • E. isDesignedAs
    Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
  • 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_69d7bdea2ca881908f379526c13b1145 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9559458dc8190bc4d6e697e99d70e completed April 10, 2026, 7:55 p.m.
PD Predicate disambiguation batch_69d9541894fc8190a0c3706a414279f0 completed April 10, 2026, 7:48 p.m.
Created at: April 9, 2026, 5:11 p.m.