Triple
T15924197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPECTRA |
E386165
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aircraft defensive aids suite |
C14080
|
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: aircraft defensive aids suite Context triple: [SPECTRA, instanceOf, aircraft defensive aids suite]
-
A.
defensive avionics system
chosen
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.
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.
-
C.
air and missile defense interceptor
An air and missile defense interceptor is a guided weapon system designed to detect, track, and destroy incoming aircraft, cruise missiles, or ballistic missiles before they reach their targets.
-
D.
combat aircraft mission system suite
A combat aircraft mission system suite is an integrated collection of avionics, sensors, communication, navigation, and weapon management subsystems that work together to plan, execute, and support military air missions.
-
E.
missile warning system
A missile warning system is a defense mechanism that detects, tracks, and alerts relevant entities to incoming missile threats to enable timely protective or countermeasure responses.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:52 a.m.