Triple

T21064631
Position Surface form Disambiguated ID Type / Status
Subject David's Sling E518933 entity
Predicate interceptorFeature P142709 FINISHED
Object hit-to-kill warhead 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: hit-to-kill warhead | Statement: [David's Sling, interceptorFeature, hit-to-kill warhead]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: interceptorFeature
Context triple: [David's Sling, interceptorFeature, hit-to-kill warhead]
  • A. integrationFeature
    Indicates that one entity provides a capability or component specifically intended to enable or support integration with another system, service, or component.
  • B. endpointFeature
    Indicates that a particular feature, capability, or characteristic is associated with, provided by, or available at a specific endpoint.
  • C. protectsFeature
    Indicates that one entity safeguards, preserves, or defends a particular feature or characteristic of another entity.
  • D. passesFeature
    Indicates that one entity successfully satisfies, verifies, or meets the criteria of a specified feature or test condition associated with another entity.
  • E. appliesToFeature
    Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
  • F. None of above. chosen

Provenance (4 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_69e0b505ef108190b25dd4033e2ff7eb completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6feb29e388190a80fa969a4daa606 completed April 21, 2026, 4:36 a.m.
PD Predicate disambiguation batch_69e5dbf9d71881908cd85dfc37db93ca completed April 20, 2026, 7:55 a.m.
PDg Predicate description generation batch_69e5e2e03d88819086f8b641656ad8b0 completed April 20, 2026, 8:25 a.m.
Created at: April 16, 2026, 2:44 p.m.