Triple
T25353970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AN/ALQ-218 receiver system |
E635769
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electronic warfare receiver system |
C407
|
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: electronic warfare receiver system Context triple: [AN/ALQ-218 receiver system, instanceOf, electronic warfare receiver 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.
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.
-
C.
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.
-
D.
heterodyne receiver
chosen
A heterodyne receiver is a radio receiver that converts an incoming signal to an intermediate frequency by mixing it with a locally generated oscillator signal to enable easier and more selective amplification and filtering.
-
E.
radar countermeasure
A radar countermeasure is a system or technique designed to deceive, disrupt, or degrade the performance of radar sensors, reducing their ability to detect, track, or identify targets.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:34 p.m.