BLACKDECK.
← Back to the world view

SOURCE STORY / newrepublic.com

Heating oil bills iran prices

Caption derived from the source URL; article headline not verified.

Encoded occurrence date: 2026-09-23Last observed: 2026-09-23 22:15 UTC

01 / OBSERVED RECORD

What happened?

GDELT encoded Fight with small arms and light weapons. Involved actors: Pennsylvania.

Location: Pennsylvania, United States

Approximate GDELT action-location centroid; not a verified affected facility. This story contains 1 coded locations; the map uses one representative location.

1encoded records grouped
1maximum source count reported by GDELT
3maximum reported mentions

These are reporting counts, not independent confirmations, casualties or disruption quantities.

Open original source ↗

02 / MULTI-LABEL CLASSIFICATION

One story. Several dimensions.

Event types

Transmission mechanisms

Potentially exposed assets

03 / CONDITIONAL BUSINESS EFFECT

What could it disrupt?

Armed disruption Crude oil & refining Production / delivery availability risk

Candidate: URL context only

Why this link exists: CAMEO 193 · Asset terms in URL: oil

Rule: blackdeck-taxonomy-2.0/asset:crude-oil/armed-disruption

Potential magnitudeHIGH · 56.0/100
availability↓ DOWNlead time↑ UPcost pressure↑ UPprice pressure↑ UP

Conditional pressure estimate; not verified physical loss or market-price impact. Evidence: MODERATE RULE MATCH.

Show model factors
event type severity
100.0
normalized evidence
0.692
mechanism strength
0.88
target sensitivity
0.92
Verified output loss (barrels/day)Not verified

Conditional pathway, not proof of an outage, commodity price move or company loss.

Watch next: Verify facility identity, lost output, inventory buffers and observed price movement.

04 / WHAT IS ACTUALLY NEW?

Escalating signal

6 similar prior source-story groups in 7 days; similar reporting on 8 dates in 14 days. This is a coverage comparison, not a count of verified recurring incidents.

Before novelty adjustment42.4review points
After novelty adjustment36.1review points

Retained new-information weight: 85.2%. Reporting persistence: 61.6/100 (coverage index only).

The model restored some attention because the coded severity or matched mechanism/asset changed. This change still needs source verification.

Repeated reporting reduces editorial novelty. It does not reduce verified physical damage or establish that a disruption remains unresolved.

Inspect the formula and limitations →