Triple
T6865606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-200 Angara/Vega/Dubna |
E158392
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | long-range air defense system |
C8470
|
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: long-range air defense system Context triple: [S-200 Angara/Vega/Dubna, instanceOf, long-range air defense system]
-
A.
ground-based air defense system
chosen
A ground-based air defense system is a coordinated set of land-deployed sensors, command-and-control elements, and weapon platforms designed to detect, track, and engage airborne threats such as aircraft, missiles, and drones.
-
B.
integrated air defence system
An integrated air defence system is a coordinated network of sensors, command and control elements, and weapon systems designed to detect, track, and engage aerial threats to protect designated airspace and assets.
-
C.
self-propelled surface-to-air missile system
A self-propelled surface-to-air missile system is a mobile, ground-based weapons platform that integrates its own propulsion, radar, and missile launch capabilities to detect, track, and engage airborne targets.
-
D.
air and missile defense interceptor
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.
-
E.
long-range land-attack missile
A long-range land-attack missile is a guided weapon system designed to strike fixed or relocatable targets deep inland from significant stand-off distances, typically launched from air, sea, or ground platforms.
- 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_69c68831e3648190a643c328122e4d43 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:21 p.m.