Record entry · Auto

Startup Battlefield

What is happening now

Meet the Startup Battlefield 200 judges who’ll decide the winner at TechCrunch Disrupt 2026
Reported claim · first reported 28 Sept 2026 · 1 claim · best-carried claim: 1 separate publisher

How well we know this

44 documents · 2 publishers · 16% contain a typed assertion · last evidence 7 Oct 2026

Gap: assertion coverage 0.159: about 84% of mentions carry no typed assertion

Added 30 Sept 2026Mentions 27Sources 7Days of coverage 16

Why this name is on the record

Startup Battlefield was added automatically on 30 Sept 2026 after 27 mentions across 7 sources over 16 days. 41% of that coverage came from a single subject area.

Reported alongside Startup Battlefield

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.

Techcrunch Disrupt · 42 shared documents
San Francisco · 38 shared documents
AI · 35 shared documents
Moscone West · 23 shared documents · no page of its own yet
Expo Hall · 15 shared documents
Ai-Powered · 12 shared documents
Disrupt Stage · 8 shared documents · no page of its own yet
OpenAI · 8 shared documents

For developers

GET https://sigb.ai/api/registry?slug=startup-battlefield

{
  "slug": "startup-battlefield",
  "state": "active",
  "detail": {
    "state": "active",
    "source": "ontology",
    "label": "startup battlefield",
    "promotedAt": "2026-09-30",
    "category": "auto",
    "evidence": {
      "mentions": 27,
      "sources": 7,
      "days": 16,
      "concentration": 0.407,
      "standAloneShare": 0.964
    }
  }
}

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

Walk the record from Startup Battlefield

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.