Triple
T8588443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defence Ground-based Air Defence Command |
E203366
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air defence unit |
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: air defence unit Context triple: [Defence Ground-based Air Defence Command, instanceOf, air defence unit]
-
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.
aviation regiment
An aviation regiment is a military unit composed of multiple aircraft squadrons or flights, along with their supporting personnel and equipment, organized to conduct coordinated air operations.
-
D.
army aviation unit
An army aviation unit is a military organization equipped with rotary- and/or fixed-wing aircraft to provide reconnaissance, air assault, transport, close air support, and other aviation capabilities in support of ground forces.
-
E.
air base squadron
An air base squadron is a military aviation unit stationed at an air base, responsible for organizing, operating, and supporting aircraft and personnel to conduct assigned air missions and base functions.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.