Triple
T20817339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AEGIS combat system |
E512476
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | integrated weapons system |
C3939
|
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: integrated weapons system Context triple: [AEGIS combat system, instanceOf, integrated weapons system]
-
A.
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.
-
B.
weapon system
chosen
A weapon system is an integrated set of components, technologies, and processes designed to detect, engage, and neutralize targets through the controlled application of force.
-
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.
integrated avionics suite
An integrated avionics suite is a cohesive collection of aircraft electronic systems—such as navigation, communication, flight control, and monitoring—designed to work together through shared hardware, software, and data networks to enhance safety, efficiency, and pilot situational awareness.
-
E.
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.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:41 p.m.