Triple
T25361611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AN/ALQ-99 |
E635982
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tactical jamming system |
C14170
|
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: tactical jamming system Context triple: [AN/ALQ-99, instanceOf, tactical jamming system]
-
A.
frequency-hopping communication system
A frequency-hopping communication system is a wireless transmission method in which the carrier rapidly switches among multiple frequency channels according to a pseudorandom sequence shared by transmitter and receiver to enhance security and resistance to interference.
-
B.
radar countermeasure
chosen
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.
-
C.
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.
-
D.
multispectral targeting system
A multispectral targeting system is an integrated sensor and processing suite that detects, tracks, and designates targets across multiple parts of the electromagnetic spectrum (e.g., visible, infrared, and radar) to enhance accuracy and situational awareness.
-
E.
military bridge-layer system
A military bridge-layer system is an armored, mobile engineering vehicle designed to rapidly deploy and retrieve temporary bridges to enable troops and vehicles to cross obstacles in combat environments.
- 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.