Triple
T32058146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warsaw Pact air defense system |
E818675
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military 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: military air defense system Context triple: [Warsaw Pact air defense system, instanceOf, military 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.
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.
-
C.
air and missile defence force
An air and missile defence force is a military organization responsible for detecting, tracking, and intercepting hostile aircraft and missiles to protect designated airspace, forces, and critical assets.
-
D.
defensive avionics system
A defensive avionics system is an integrated suite of onboard sensors, processors, and countermeasure devices designed to detect, identify, and protect an aircraft from hostile threats such as radar, missiles, and electronic attacks.
-
E.
military radar system
A military radar system is an integrated sensor platform that emits and receives electromagnetic signals to detect, track, and classify airborne, maritime, or ground targets for surveillance, targeting, and defense operations.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:21 a.m.