Record entry · Auto

Gartner

Added 30 Sept 2026Mentions 81Sources 40Days of coverage 31

Why this name is on the record

Gartner was added automatically on 30 Sept 2026 after 81 mentions across 40 sources over 31 days. 21% of that coverage came from a single subject area.

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

AIAnthropicOpenAIAmazonGoogleagentic AIMicrosoftCryptoAI agent
  • AI · 119 shared documents
  • AI agents · 41 shared documents · no page of its own yet
  • Anthropic · 38 shared documents
  • OpenAI · 34 shared documents
  • Amazon · 32 shared documents
  • Google · 32 shared documents
  • agentic AI · 30 shared documents
  • Microsoft · 30 shared documents
  • Crypto · 28 shared documents
  • AI agent · 26 shared documents

For developers

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

{
  "slug": "gartner",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "gartner",
    "promotedAt": "2026-09-30",
    "category": "auto",
    "evidence": {
      "mentions": 81,
      "sources": 40,
      "days": 31,
      "concentration": 0.21,
      "standAloneShare": 0.886
    }
  }
}

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

Walk the record from Gartner

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.

Gartner

Entity.

Evidence
127 documents · 55 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 27 Apr 2026, last seen 8 Oct 2026
Measured
17% of mentions say something specific about it; the rest only name it
As of
8 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