Triple
T30122110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO E-3A Component |
E765587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airborne early warning and control unit |
C42026
|
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: airborne early warning and control unit Context triple: [NATO E-3A Component, instanceOf, airborne early warning and control unit]
-
A.
airborne early warning squadron
chosen
An airborne early warning squadron is a military aviation unit equipped with specialized radar aircraft to detect, track, and relay information on aerial and surface threats, providing command and control support to friendly forces.
-
B.
airborne signals unit
An airborne signals unit is a specialized military or intelligence team equipped on aircraft to detect, intercept, analyze, and relay electronic and communications signals from the air.
-
C.
aviation support unit
An aviation support unit is an organizational entity that provides maintenance, logistics, ground handling, and operational assistance to ensure the effective and safe functioning of aircraft and flight operations.
-
D.
airborne forces unit
An airborne forces unit is a military formation trained, equipped, and organized to deploy rapidly by air and conduct combat or support operations after insertion, typically by parachute, air assault, or air landing.
-
E.
combat aviation unit
A combat aviation unit is an organized group of military aircraft, aircrew, and support personnel structured to plan, execute, and sustain offensive and defensive air 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:13 p.m.