Triple

T18644329
Position Surface form Disambiguated ID Type / Status
Subject WR E455764 entity
Predicate majorRoute P385 FINISHED
Object Mumbai–Surat–Vadodara corridor NE NERFINISHED

How this triple was built (3 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: Mumbai–Surat–Vadodara corridor | Statement: [WR, majorRoute, Mumbai–Surat–Vadodara corridor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mumbai–Surat–Vadodara corridor
Context triple: [WR, majorRoute, Mumbai–Surat–Vadodara corridor]
  • A. Mumbai–Bengaluru corridor
    The Mumbai–Bengaluru corridor is a major economic and transport axis in western and southern India, linking the financial hub of Mumbai with the technology and industrial center of Bengaluru through a network of highways and rail routes.
  • B. Mumbai–Ahmedabad route
    The Mumbai–Ahmedabad route is a major rail and transport corridor in western India connecting the metropolitan cities of Mumbai and Ahmedabad.
  • C. Delhi–Mumbai route
    The Delhi–Mumbai route is one of India’s busiest and most important railway corridors, connecting the national capital with the country’s financial hub through major cities across northern and western India.
  • D. Ahmedabad–Vadodara line
    The Ahmedabad–Vadodara line is a key railway corridor in the Indian state of Gujarat that connects the major cities of Ahmedabad and Vadodara and forms part of the busy Western Railway network.
  • E. Noida–Agra–Lucknow corridor
    The Noida–Agra–Lucknow corridor is a major expressway-based economic and transportation belt in Uttar Pradesh, India, linking the Delhi NCR region with Agra and the state capital Lucknow.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Mumbai–Surat–Vadodara corridor
Target entity description: The Mumbai–Surat–Vadodara corridor is a heavily industrialized and densely populated economic and transportation belt in western India, linking major commercial hubs in Maharashtra and Gujarat.
  • A. Mumbai–Bengaluru corridor
    The Mumbai–Bengaluru corridor is a major economic and transport axis in western and southern India, linking the financial hub of Mumbai with the technology and industrial center of Bengaluru through a network of highways and rail routes.
  • B. Mumbai–Ahmedabad route
    The Mumbai–Ahmedabad route is a major rail and transport corridor in western India connecting the metropolitan cities of Mumbai and Ahmedabad.
  • C. Delhi–Mumbai route
    The Delhi–Mumbai route is one of India’s busiest and most important railway corridors, connecting the national capital with the country’s financial hub through major cities across northern and western India.
  • D. Ahmedabad–Vadodara line
    The Ahmedabad–Vadodara line is a key railway corridor in the Indian state of Gujarat that connects the major cities of Ahmedabad and Vadodara and forms part of the busy Western Railway network.
  • E. Noida–Agra–Lucknow corridor
    The Noida–Agra–Lucknow corridor is a major expressway-based economic and transportation belt in Uttar Pradesh, India, linking the Delhi NCR region with Agra and the state capital Lucknow.
  • F. None of above. chosen

Provenance (2 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_69d8d38ea1e88190997e9b231190ba6f completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5500c36188190bfdd7aca73f3c006 completed April 19, 2026, 9:58 p.m.
Created at: April 10, 2026, 11:47 a.m.