Ukrainian drones sink Russian-flag container ship Yanina in Black Sea
- Source
- Container News
- Source link
- https://container-news.com/ukrainian-drones-sink-russian-flag-the-container-ship-yanina-in-black-sea/
- Published
- 2026-08-03 07:31:29
- Discovered by ProcIntel
- 2026-08-03 08:58:36
- Category
- Freight, Shipping & Logistics
- Geography
- Global
- Organisations
- —
- Review status
- Pending
- Record type
- REAL
Summary
<a href="https://container-news.com/ukrainian-drones-sink-russian-flag-the-container-ship-yanina-in-black-sea/" title="Ukrainian drones sink Russian-flag container ship Yanina in Black Sea" rel="nofollow"><img width="300" height="163" src="https://container-news.com/wp-content/uploads/2026/08/tjuk-300x163.jpg" class="webfeedsFeaturedVisual wp-post-image" alt="Ukrainian naval drones sank the container ship Yanina in the Black Sea" style="float: left; margin-right: 5px;" link_thumbnail="1" decoding="async" srcset="https://container-news.com/wp-content/uploads/2026/08/tjuk-300x163.jpg 300w, https://container-news.com/wp-content/uploads/2026/08/tjuk-150x81.jpg 150w, https://container-news.com/wp-content/uploads/2026/08/tjuk-240x130.jpg 240w, https://container-news.com/wp-content/uploads/2026/08/tjuk.jpg 602w" sizes="(max-width: 300px) 100vw, 300px" /></a><p>Ukrainian naval drones have sunk the Russian-flagged container ship Yanina in the Black Sea, according to statements from both Ukraine and Russia. The vessel was reportedly struck by two drones overnight on 1 August while sailing around 130 nautical miles from the Russian port of Novorossiysk. Yanina was operated by Russian logistics company FESCO, which […]</p> <p>The post <a href="https://container-news.com/ukrainian-drones-sink-russian-flag-the-container-ship-yanina-in-black-sea/">Ukrainian drones sink Russian-flag container ship Yanina in Black Sea</a> appeared first on <a href="https://container-news.com">Container News</a>.</p>
Procurement Relevance Gate
- logistics_freight_transport (weight 12) — matched on "port"
- geographic_exposure (weight 8) — matched on "1 linked geography"
Initial Signal Assessment ProcIntel's automatic, provisional read of this individual Signal -- Initial Significance and Initial Confidence, computed deterministically before any Event extraction or human review.
A provisional, automatically-computed reading of this individual Signal, before Event extraction or human review. Not a final rating.
- Initial Significance
- 1 · Low (18.0/100)
- Initial Confidence
- 2 · Low (26.5/100)
- Data sufficiency Whether enough structured evidence exists to trust this Signal's Initial Confidence reading. 'Sufficient' has no cap; 'Partial' and 'Insufficient' cap Confidence until more evidence is available; 'Not Assessed' means the Signal did not pass the Relevance Gate.
- Partial
- Strongest contributor
- Procurement Impact
- Limiting factor
- Likely Event Severity
Initial Significance Low (18.0/100). Strongest contributor: Procurement Impact (6.0/30 points). Limiting factor: Likely Event Severity (3.0/30 points). Initial Confidence Low (26.5/100, data sufficiency: Partial). Strongest contributor: Source Authority (20.0/40 points). Limiting factor: Corroboration (2.5/25 points).
- No likely Event type matched; a low contextual baseline was applied.
- No eligible (non-geographic, non-fictional) entities were linked to this Signal.
- no matched Event type
- no actor entities (only attribution/metadata, if any)
- no actor content-derived geography
- single source only
- Entities were mentioned as context or document attribution rather than as actors in the reported development, so they did not increase Initial Confidence.
- Geographies were mentioned only in diplomatic reaction, commentary or background context rather than as the actor, event location or affected party in the reported development, so they did not increase Initial Confidence.
- Only source-level geography metadata was available.
- Source metadata did not contribute to Initial Confidence.
- 1 distinct hedging pattern(s) matched (capped at 20).
Methodology signal_scoring_v1 — calculated 2026-08-03 16:30:17.