Triple

T8241704
Position Surface form Disambiguated ID Type / Status
Subject Ola Outstation E192550 entity
Predicate associatedWith P37 FINISHED
Object Ola Mini E191356 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: Ola Mini | Statement: [Ola Outstation, associatedWith, Ola Mini]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ola Mini
Context triple: [Ola Outstation, associatedWith, Ola Mini]
  • A. Ola Micro chosen
    Ola Micro is a budget-friendly ride option from Indian ride-hailing company Ola, offering low-cost cab services for short-distance urban travel.
  • B. Ola Prime
    Ola Prime is a premium ride category offered by Ola, featuring higher-end sedans and added comfort compared to its standard services.
  • C. Ola Auto
    Ola Auto is a ride-hailing service segment of Ola Cabs that connects passengers with auto-rickshaw drivers via the Ola mobile app.
  • D. Ola
    Ola is a major Indian ride-hailing and mobility platform offering cab, auto-rickshaw, and other transportation services via its mobile app.
  • E. Ola
    Ola is a small urban locality in Russia’s Magadan Oblast, situated in the Russian Far East along the Sea of Okhotsk.
  • 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_69ca82dc8f148190a2c75a98501a7b91 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb783f67708190a4e1c4078c3a6fb0 completed March 31, 2026, 7:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd6801eaec8190a104ac6b08030376 completed April 1, 2026, 6:46 p.m.
Created at: March 30, 2026, 5:47 p.m.