Entity · moving across domains

Hormuz

The Strait of Hormuz — the narrow waterway between Iran and Oman through which roughly a fifth of the world's oil passes.

As of 7 Oct 2026

Who Hormuz moves with

Names most often reported alongside it; bigger circles and heavier lines mean more shared documents. A dashed circle has no page of its own yet.

IranTrumpMiddle EastSaudi ArabiaUnited StatesIsraelYemenRed Sea
  • Iran · 2,500 shared documents
  • Oil · 2,104 shared documents · no page of its own yet
  • Trump · 1,344 shared documents
  • Middle East · 1,328 shared documents
  • Saudi Arabia · 1,139 shared documents
  • United States · 1,092 shared documents
  • Israel · 967 shared documents
  • Yemen · 913 shared documents
  • Red Sea · 785 shared documents
  • Oil Prices · 735 shared documents · no page of its own yet

Story momentum

Rising

Daily mentions +478% from 23 Aug 2026 to 7 Oct 2026, between 19 and 191 a day

How often tracked coverage mentions Hormuz, day by day.

Market price, cited

18% Yes

priced 7 Oct 2026

the market: 32% → 18% Yes (-14pts, from 23 Aug 2026 to 7 Oct 2026)

on “Strait of Hormuz traffic returns to normal by December 31?”

The day’s closing price on this market, and how it moved. The number is the market’s own. Ask about Hormuz

“Strait of Hormuz traffic returns to normal by December 31?”: the market's own price; the venue link is not stored with it

Coverage volume and market price are separate measures.

For developers

Call the get_entity MCP tool at https://sigb.ai/api/mcp with name hormuz.

{
  "name": "hormuz",
  "label": "Hormuz",
  "asOf": "2026-10-07",
  "mentions": 156,
  "domains": 43,
  "coverageTrend": "rising",
  "marketPrice": {
    "question": "Strait of Hormuz traffic returns to normal by December 31?",
    "yesPct": 18,
    "pricedOn": "2026-10-07",
    "attribution": "the market's own price"
  },
  "whereFrom": {
    "level": "counts",
    "label": "156 mentions across 43 domains",
    "children": [
      {
        "level": "reports",
        "label": "4 reports drawn on this page, each with its link",
        "children": {
          "count": 4,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "domains",
        "label": "43 coverage domains",
        "children": {
          "count": 18,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "not shown",
        "label": "The other 152 mentions",
        "edge": "counted daily from tracked coverage; single mentions are not listed one by one"
      }
    ]
  }
}

The figures on this page, as data. The tool returns the full entity record.

Walk the record from Hormuz

Open where it comes from, follow a claim or a related name, and use the trail to come back. Every step says what it is, how it stands and when. Machines read the same record.

denver

Entity, reached from Hormuz.

Evidence
381 documents · 139 separate publishers · a mention shows the name is in use, not that any claim about it is true
Standing
A name from our starting list; its record is kept up to date automatically from coverage
Time
first seen 28 Apr 2026, last seen 7 Oct 2026
Measured
29% of mentions say something specific about it; the rest only name it
As of
7 Oct 2026
10 links from here

For machines: this record as JSON

Watch this

What the coverage says

Recent reporting that names Hormuz, newest first. Open any row to follow it to the original article.

Evidence tiers: primary source = an official public record · attributed = a named outlet, receipt linked · lead = observed, not yet receipted.

Other questions markets are asking

Prices are the market’s own, cited with the venue.

What it connects to

Related records.

Events in motion

Events that involve Hormuz.

What markets are asking about these events

Pull a thread

Ask about HormuzWatch Hormuz

Story momentum counts mentions in tracked coverage. Prices are the market’s own, cited with the venue. Informational only, not advice. As of 7 Oct 2026.