Triple
T33677961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAAMS |
E862810
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | naval 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: naval air defense system Context triple: [PAAMS, instanceOf, naval 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.
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.
-
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.
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.
-
E.
ground-based air defense system
A ground-based air defense system is a coordinated set of land-deployed sensors, command-and-control elements, and weapon platforms designed to detect, track, and engage airborne threats such as aircraft, missiles, and drones.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:43 a.m.