Triple
T36520377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Cat missile system |
E900163
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | naval air-defence system |
C26997
|
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-defence system Context triple: [Sea Cat missile system, instanceOf, naval air-defence system]
-
A.
naval defense system
chosen
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.
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.
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.
naval missile system
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.
coastal defense missile system
A coastal defense missile system is a land-based military installation designed to detect, track, and engage hostile naval targets approaching a nation's shoreline using guided missiles and integrated sensor networks.
- 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_69f76e5eedb88190a393b8c623f71dd7 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.