Record entry · South Korea

Samsung Heavy Industries

What is happening now

Nothing reported: the record holds no registered event and no claim that names this.

How well we know this

20 documents · 9 publishers · 0% contain a typed assertion · last evidence 11 Oct 2026

  • Gap: assertion coverage 0: about 100% of mentions carry no typed assertion
Added 11 Oct 2026Mentions 20Sources 9Days of coverage 15

Why this name is on the record

Samsung Heavy Industries was added automatically on 11 Oct 2026 after 20 mentions across 9 sources over 15 days. 60% of that coverage came from a single subject area.

Reported alongside Samsung Heavy Industries

  • LNG · 8 shared documents · no page of its own yet

For developers

GET https://api.signalbureau.ai/api/registry?slug=samsung-heavy-industries

{
  "slug": "samsung-heavy-industries",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "samsung heavy industries",
    "promotedAt": "2026-10-11",
    "category": "south_korea",
    "evidence": {
      "mentions": 20,
      "sources": 9,
      "days": 15,
      "concentration": 0.6,
      "standAloneShare": 0.9
    }
  }
}

The record behind this page, as data. The live response also carries the registry date and version.

Walk the record from Samsung Heavy Industries

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.

Samsung Heavy Industries

Entity.

Evidence
20 documents · 9 separate publishers · a mention shows the name is in use, not that any claim about it is true
Standing
Added automatically from coverage
Time
first seen 5 Sept 2026, last seen 11 Oct 2026
Measured
0% of mentions say something specific about it; the rest only name it
As of
11 Oct 2026
1 link from here

Who it moves with: the 1 name is in the map above.

What is claimed about it (0)

none on file at this cutoff

Situations it is named in (0)

none on file at this cutoff

For machines: this record as JSON

Watch this