Record entry · Auto

Geforce RTX

What is happening now

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

How well we know this

78 documents · 19 publishers · 0% contain a typed assertion · last evidence 19 Oct 2026

Gap: assertion coverage 0: about 100% of mentions carry no typed assertion

Added 30 Sept 2026Mentions 20Sources 8Days of coverage 11

Why this name is on the record

Geforce RTX was added automatically on 30 Sept 2026 after 20 mentions across 8 sources over 11 days. 70% of that coverage came from a single subject area.

Reported alongside Geforce RTX

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.

RTX · 78 shared documents · no page of its own yet
Nvidia · 74 shared documents
AI · 53 shared documents
AMD · 52 shared documents · no page of its own yet
GPUs · 51 shared documents · no page of its own yet
Intel · 35 shared documents
Dlss · 31 shared documents
Radeon · 29 shared documents
Asus · 24 shared documents
Vram · 24 shared documents

For developers

GET https://api.signalbureau.ai/api/registry?slug=geforce-rtx

{
  "slug": "geforce-rtx",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "geforce rtx",
    "promotedAt": "2026-09-30",
    "category": "auto",
    "evidence": {
      "mentions": 20,
      "sources": 8,
      "days": 11,
      "concentration": 0.7,
      "standAloneShare": 0.621
    }
  }
}

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

Walk the record from Geforce RTX

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.

geforce RTX

Entity.

Evidence: 78 documents · 19 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 5 Sept 2026, last seen 19 Oct 2026
Measured: 0% of mentions say something specific about it; the rest only name it
As of: 20 Oct 2026