Triple
T34495762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SeaRAM |
E885600
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | shipboard air-defense system |
C49079
|
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: shipboard air-defense system Context triple: [SeaRAM, instanceOf, shipboard air-defense system]
-
A.
naval defense system
A naval defense system is an integrated network of sensors, weapons, platforms, and command-and-control components designed to detect, deter, and neutralize maritime threats to ships, fleets, and coastal assets.
-
B.
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.
-
C.
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.
-
D.
naval missile system
chosen
A naval missile system is an integrated shipborne weapon platform designed to detect, track, and engage air, surface, or subsurface threats using guided missiles coordinated by sensors and fire-control systems.
-
E.
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.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.