Triple
T9593853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Viper missile system |
E231482
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | naval air-defense system |
C1870
|
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: naval air-defense system Context triple: [Sea Viper missile system, instanceOf, naval air-defense 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.
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.
air-defence warship
An air-defence warship is a naval vessel specifically equipped with advanced radar, sensors, and missile systems to detect, track, and neutralize airborne threats, protecting itself and other ships in a fleet.
-
D.
naval combat system component
chosen
A naval combat system component is an individual hardware or software element—such as a sensor, weapon, processor, or communication module—that contributes specific functionality to the detection, tracking, engagement, or control capabilities of an integrated maritime warfare system.
-
E.
naval arsenal
A naval arsenal is a specialized military facility where warships are built, repaired, equipped, and supplied with weapons, ammunition, and other naval stores.
- 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:07 p.m.