Skip to main content
Applied IntuitionLinkedIn

Applied Intui engineer explains how labeled data loops back to training fleets.

Source: Autobound Signal API · 76 signals tracked for Applied Intuition · updated

Get Applied Intuition's live signals in Claude or ChatGPT, or by API

AskWhat changed at Applied Intuition this week? Use Autobound signals for appliedintuition.com.

Source

LinkedInOct 28, 2026
likes
104
comments
5

Post

How does labeled data become a model back on the road? Shiyan Xu, an engineer on our Data Engine team, breaks down how we take labeled data through curation, scenarios, data loading, training, and evaluation, all the way back to the fleet, across hundreds of petabytes of multimodal data from automotive, trucking, mining, and robotics fleets. Closing that loop comes down to a few key design choices: 👉 Choosing segments to feed the model: Curation runs selection criteria, like nighttime driving with a cut-in under two seconds, against a curation table hundreds of columns wide. Scenarios no metric or label covers can be found by searching clip embeddings with text or an example clip. 👉 Building scenarios for training: Each scenario bundles aligned frames, labels, map, and route into one row. Lance’s blob v2 API makes each scenario’s blob payload easy to work with: written and versioned with the row, read only when needed. Data evolution adds new fields without rewriting existing files. 👉 Turning scenarios into model inputs: Lance’s random access lets training sample rows non-sequentially in small, scattered batches, with each batch fetched as a single take. Checkpointing lets a restarted job pick up where the sampler left off instead of replaying. 👉 Training in two stages: Imitation learning first teaches the model to drive like the fleet’s drivers, then reinforcement...

Keep reading with a free account

The rest of this post, and every signal for Applied Intuition, is in your free account.

Extracted by Autobound

From the Signal API record
Signal
LinkedIn

What this signalsCompany posts often show what the team is pushing right now.

More LinkedIn signals at other companies

The full record

From the Signal API record

Topics and mentions

Tags

  • Machine Learning
  • Artificial Intelligence
  • Data Management
  • Events

Initiatives

  • presenting at Reverie 2026

Technologies named

  • LanceDB
  • Lance’s blob v2 API

Extraction

Detected
Oct 28, 2026
signal_type
linkedin-post-company
signal_subtype
linkedinPost

Use this data

Get every LinkedIn signal for Applied Intuition and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Applied Intuition this week?”

  2. Send it to your own tools

    The Signal API returns LinkedIn signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full linkedin-post-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/d30e0b57-c084-44f7-a5dd-dc6fc414abd7 returns this record as JSON. POST /v1/companies/enrich returns every signal for appliedintuition.com.

{
  "signal_id": "d30e0b57-c084-44f7-a5dd-dc6fc414abd7",
  "signal_type": "linkedin-post-company",
  "signal_subtype": "linkedinPost",
  "detected_at": "2026-10-28T18:17:22.168+00:00",
  "company": {
    "name": "Applied Intuition",
    "domain": "appliedintuition.com"
  },
  "data": {
    "tags": [
      "Machine Learning",
      "Artificial Intelligence",
      "Data Management",
      "Events"
    ],
    "summary": "Applied Intui engineer explains how labeled data loops back to training fleets.",
    "post_url": "https://www.linkedin.com/posts/applied-intuition-inc_reverie2026-activity-7521273924735746048-jmMn",
    "num_likes": 104,
    "post_text": "How does labeled data become a model back on the road?\n\nShiyan Xu, an engineer on our Data Engine team, breaks down how we take labeled data through curation, scenarios, data loading, training, and evaluation, all the way back to the fleet, across hundreds of petabytes of multimodal data from automotive, trucking, mining, and robotics fleets.\n\nClosing that loop comes down to a few key design choices:\n\n👉 Choosing segments to feed the model: Curation runs selection criteria, like nighttime driving with a cut-in under two seconds, against a curation table hundreds of columns wide. Scenarios no metric or label covers can be found by searching clip embeddings with text or an example clip.\n\n👉 Building scenarios for training: Each scenario bundles aligned frames, labels, map, and route into one row. Lance’s blob v2 API makes each scenario’s blob payload easy to work with: written and versioned with the row, read only when needed. Data evolution adds new fields without rewriting existing files.\n\n👉 Turning scenarios into model inputs: Lance’s random access lets training sample rows non-sequentially in small, scattered batches, with each batch fetched as a single take. Checkpointing lets a restarted job pick up where the sampler left off instead of replaying.\n\n👉 Training in two stages: Imitation learning first teaches the model to drive like the fleet’s drivers, then reinforcement...",
    "initiatives": [
      {
        "topic": "presenting at Reverie 2026",
        "urgency": 0.7
      }
    ],
    "posted_date": "2026-10-28T18:17:22.168Z",
    "num_comments": 5,
    "technologies_mentioned": [
      {
        "name": "LanceDB",
        "status": "building_on"
      },
      {
        "name": "Lance’s blob v2 API",
        "status": "considering"
      }
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.