Triple
T8234323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AJP-3.22 Allied Joint Doctrine for Countering Unmanned Aircraft Systems |
E192366
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | counter‑UAS doctrine |
C14931
|
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: counter‑UAS doctrine Context triple: [AJP-3.22 Allied Joint Doctrine for Countering Unmanned Aircraft Systems, instanceOf, counter‑UAS doctrine]
-
A.
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.
-
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.
airspace security operation
chosen
An airspace security operation is a coordinated set of activities, technologies, and procedures designed to monitor, control, and protect designated airspace from unauthorized or hostile aerial threats.
-
D.
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.
-
E.
missile defense radar
A missile defense radar is a specialized sensor system that detects, tracks, and characterizes incoming missiles to support timely interception and defense actions.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:46 p.m.