Triple
T32595092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Headache |
E833180
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electronic countermeasure |
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: electronic countermeasure Context triple: [Headache, instanceOf, electronic countermeasure]
-
A.
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.
-
B.
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.
-
C.
missile defense command and control system
A missile defense command and control system is an integrated network of sensors, communication links, decision-support tools, and engagement controls that detects, tracks, evaluates, and coordinates responses to missile threats in real time.
-
D.
anti-radiation missile
An anti-radiation missile is a guided weapon designed to detect, home in on, and destroy enemy radar or other radio-frequency emitters by tracking their electromagnetic emissions.
-
E.
missile defense program
A missile defense program is an organized system of technologies, policies, and operations designed to detect, track, intercept, and neutralize incoming missiles before they reach their intended 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:05 a.m.