Triple
T10041340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skynex air defence system |
E205301
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | modular 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: modular air defense system Context triple: [Skynex air defence system, instanceOf, modular air defense system]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 8:55 p.m.