Entity

Techcrunch Disrupt

A topic on our watch list — we track its coverage across 2 coverage verticals, including AI News and Venture.

As of 29 Oct 2026Last evidence 27 Oct 2026

What is happening now

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

What changed

Attention Fading: 3 mentions on 27 Oct 2026, against 11 on 6 Oct 2026 (-73%).
State No change in coverage state or wire tier recorded since 17 Oct 2026.
Claims No claim first reported since 28 Oct 2026.

How well we know this

165 documents · 10 publishers · 8% contain a typed assertion · last evidence 27 Oct 2026

Gap: assertion coverage 0.079: about 92% of mentions carry no typed assertion

In this snapshot’s daily coverage:

Reported alongside Techcrunch Disrupt

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.

AI · 133 shared documents
San Francisco · 115 shared documents · no page of its own yet
Startup Battlefield · 83 shared documents · no page of its own yet
Moscone West · 67 shared documents · no page of its own yet
OpenAI · 41 shared documents
Anthropic · 33 shared documents
Disrupt Stage · 30 shared documents · no page of its own yet
AI agents · 26 shared documents
Google · 26 shared documents
Amazon · 23 shared documents

Story momentum

Fading

The word compares 3 mentions on 27 Oct 2026 with 11 on 6 Oct 2026 (-73%); a change of less than 8% either way reads Steady.

Daily mentions -62% from 18 Sept 2026 to 27 Oct 2026, between 3 and 29 a day

How often tracked coverage mentions Techcrunch Disrupt, day by day.

Market price, cited

Not priced yet

No open prediction market prices a question materially about Techcrunch Disrupt yet. Ask about Techcrunch Disrupt

No market price on file: no prediction market prices a question about this name yet

Coverage volume and market price are separate measures.

For developers

This page is also an object: GET https://sigb.ai/api/v1/node/e/9aec7897f6145247cd45dc2a returns the same record as sb.node.v1. Or call the get_entity MCP tool at https://sigb.ai/api/mcp with name techcrunch disrupt.

{
  "name": "techcrunch disrupt",
  "label": "Techcrunch Disrupt",
  "asOf": "2026-10-29",
  "mentions": 70,
  "outlets": 5,
  "domains": 2,
  "node": {
    "id": "sb:e/9aec7897f6145247cd45dc2a",
    "schema": "sb.node.v1",
    "rest": "https://sigb.ai/api/v1/node/e/9aec7897f6145247cd45dc2a",
    "knowledgeCutoff": "2026-10-29T23:27:11.436223+00:00",
    "snapshot": "this deploy's committed data files (commit not exposed in this runtime)"
  },
  "coverageTrend": "fading",
  "history": {
    "since": "2026-10-17T15:52:40.940749+00:00",
    "changes": 0
  },
  "whereFrom": {
    "level": "counts",
    "label": "70 mentions across 2 domains",
    "children": [
      {
        "level": "reports",
        "label": "6 reports drawn on this page, each with its link",
        "children": {
          "count": 6,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "domains",
        "label": "2 coverage domains",
        "children": {
          "count": 2,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "not shown",
        "label": "The other 64 mentions",
        "edge": "counted daily from tracked coverage; single mentions are not listed one by one"
      }
    ]
  }
}

The figures on this page, as data. The tool returns the full entity record.

Events involving Techcrunch Disrupt

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

Walk the record from Techcrunch Disrupt

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.