Triple
T33759706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Sea Sparrow Project |
E865073
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | missile system consortium |
C59592
|
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: missile system consortium Context triple: [NATO Sea Sparrow Project, instanceOf, missile system consortium]
-
A.
missile defense command and control system
A missile defense command and control system is an integrated network of sensors, communication links, decision-support tools, and engagement controls that detects, tracks, evaluates, and coordinates responses to missile threats in real time.
-
B.
missile launch system
A missile launch system is an integrated hardware and software framework that prepares, arms, targets, and fires missiles while managing safety, authorization, and trajectory control.
-
C.
defence industry consortium
chosen
A defence industry consortium is a collaborative alliance of companies, research institutions, and sometimes government agencies that coordinate resources, expertise, and technologies to develop, produce, and support defense-related products and services.
-
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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.