Triple
T25361610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AN/ALQ-99 |
E635982
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airborne electronic warfare system |
C14046
|
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 electronic warfare system Context triple: [AN/ALQ-99, instanceOf, airborne electronic warfare system]
-
A.
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.
-
B.
airborne radar system
An airborne radar system is an integrated aircraft-mounted sensor suite that emits radio waves and processes their reflections to detect, track, and characterize objects or terrain in the surrounding air and ground environment.
-
C.
avionics system
chosen
An avionics system is an integrated collection of electronic hardware and software on an aircraft that manages navigation, communication, monitoring, and control functions to ensure safe and efficient flight operations.
-
D.
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.
-
E.
electronic warfare command
An electronic warfare command is an organizational unit responsible for planning, coordinating, and executing operations that use the electromagnetic spectrum to detect, disrupt, deceive, or protect against adversary electronic systems.
- 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:36 p.m.