Triple

T21344550
Position Surface form Disambiguated ID Type / Status
Subject Orange Line (Nagpur Metro) E526294 entity
Predicate system P730 FINISHED
Object Nagpur Metro NE NERFINISHED

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: Nagpur Metro | Statement: [Orange Line (Nagpur Metro), system, Nagpur Metro]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nagpur Metro
Context triple: [Orange Line (Nagpur Metro), system, Nagpur Metro]
  • A. Nagpur Metro chosen
    Nagpur Metro is a rapid transit system serving the city of Nagpur in Maharashtra, India, designed to improve urban mobility and reduce traffic congestion.
  • B. Pune Metro
    Pune Metro is a rapid transit system serving the Indian city of Pune and its surrounding Pimpri-Chinchwad metropolitan region.
  • C. Navi Mumbai Metro
    Navi Mumbai Metro is a rapid transit system serving the planned city of Navi Mumbai in the Mumbai Metropolitan Region, designed to improve urban connectivity and reduce traffic congestion.
  • D. Mumbai Metro
    Mumbai Metro is a rapid transit system serving the Mumbai metropolitan region, designed to alleviate congestion and complement the city’s suburban railway network.
  • E. Ahmedabad Metro
    Ahmedabad Metro is a rapid transit system serving the city of Ahmedabad and its surrounding areas in the Indian state of Gujarat.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e0b51c33048190ab27cede74ef798c completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8a853e50c81909f8854eadf053049 completed April 22, 2026, 10:52 a.m.
Created at: April 16, 2026, 4:44 p.m.