Triple
T8588444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defence Ground-based Air Defence Command |
E203366
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ground-based air defence command |
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: ground-based air defence command Context triple: [Defence Ground-based Air Defence Command, instanceOf, ground-based air defence command]
-
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.
regional air command
A regional air command is a military organizational unit responsible for planning, directing, and controlling air operations within a specific geographic area.
-
D.
airborne command post
An airborne command post is an aircraft equipped with advanced communications, surveillance, and control systems that enables military or government leaders to direct operations and maintain command and control while in flight.
-
E.
Luftwaffe command position
A Luftwaffe command position is an organizational role within the German air force hierarchy responsible for directing air operations, managing resources, and implementing strategic and tactical decisions.
- 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.