Record entry · Auto

Npus

Added 6 Oct 2026Mentions 29Sources 16Days of coverage 15

Why this name is on the record

Npus was added automatically on 6 Oct 2026 after 29 mentions across 16 sources over 15 days. 38% of that coverage came from a single subject area.

Who Npus 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.

AISemiconductorNvidiaChinaApple
  • AI · 32 shared documents
  • GPUs · 20 shared documents · no page of its own yet
  • Semiconductor · 19 shared documents
  • Nvidia · 17 shared documents
  • Cpus · 16 shared documents · no page of its own yet
  • China · 14 shared documents
  • Qualcomm · 12 shared documents · no page of its own yet
  • AMD · 12 shared documents · no page of its own yet
  • Apple · 12 shared documents
  • edge AI · 11 shared documents · no page of its own yet

For developers

GET https://sigb.ai/api/registry?slug=npus

{
  "slug": "npus",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "npus",
    "promotedAt": "2026-10-06",
    "category": "auto",
    "evidence": {
      "mentions": 29,
      "sources": 16,
      "days": 15,
      "concentration": 0.379,
      "standAloneShare": 0.853
    }
  }
}

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

Walk the record from Npus

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.

Npus

Entity.

Evidence
34 documents · 16 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 13 Aug 2026, last seen 5 Oct 2026
Measured
15% of mentions say something specific about it; the rest only name it
As of
6 Oct 2026
10 links from here

Who it moves with: the 10 names are 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