Triple

T1482204
Position Surface form Disambiguated ID Type / Status
Subject Bolt E30982 entity
Predicate competitor P1375 FINISHED
Object Lyft E7323 NE FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Lyft | Statement: [Bolt, competitor, Lyft]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lyft
Context triple: [Bolt, competitor, Lyft]
  • A. Lyft chosen
    Lyft is a major American ride-hailing and transportation company that connects passengers with drivers through a mobile app platform.
  • B. Uber
    Uber is a global ride-hailing and technology company that connects passengers with drivers through a mobile app and has expanded into food delivery and freight services.
  • C. Uber Pro
    Uber Pro is a rewards and loyalty program that provides benefits and incentives to Uber drivers based on their performance and activity.
  • D. Careem
    Careem is a Dubai-based ride-hailing and delivery company operating across the Middle East, North Africa, and South Asia, acquired by Uber to expand its presence in the region.
  • E. Didi Chuxing
    Didi Chuxing is a major Chinese ride-hailing and mobility technology company offering app-based transportation, taxi, and related services across numerous cities in China and abroad.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69a498fe55a88190ab7f9e40ace88e49 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c6782f088190930d25a56161e2b3 completed March 1, 2026, 11:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad36ffd8808190894f2139ae12204e completed March 8, 2026, 8:44 a.m.
Created at: March 1, 2026, 8:11 p.m.