Triple
T24083967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exoatmospheric Kill Vehicle |
E596583
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hit-to-kill interceptor payload |
C6864
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: hit-to-kill interceptor payload Context triple: [Exoatmospheric Kill Vehicle, instanceOf, hit-to-kill interceptor payload]
-
A.
ballistic missile payload system
A ballistic missile payload system is the integrated assembly of warheads, guidance interfaces, deployment mechanisms, and protective structures designed to deliver and release destructive or specialized payloads to a designated target along a ballistic trajectory.
-
B.
anti-armor missile
An anti-armor missile is a guided munition designed specifically to detect, track, and destroy armored targets such as tanks and armored vehicles using high-penetration warheads.
-
C.
air and missile defense interceptor
chosen
An air and missile defense interceptor is a guided weapon system designed to detect, track, and destroy incoming aircraft, cruise missiles, or ballistic missiles before they reach their targets.
-
D.
low-collateral damage munition
A low-collateral damage munition is a precision weapon specifically designed to minimize unintended harm to nearby people, structures, and infrastructure while effectively engaging its intended target.
-
E.
infrared homing missile
An infrared homing missile is a guided weapon that detects and tracks the infrared radiation (heat) emitted by a target to autonomously steer itself toward and destroy it.
- F. None of above.
Provenance (1 batch)
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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 10:44 p.m.