Triple

T21232602
Position Surface form Disambiguated ID Type / Status
Subject Mayapuri E523259 entity
Predicate hasMetroStation P522 FINISHED
Object Mayapuri metro station 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: Mayapuri metro station | Statement: [Mayapuri, hasMetroStation, Mayapuri metro station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mayapuri metro station
Context triple: [Mayapuri, hasMetroStation, Mayapuri metro station]
  • A. Mayapuri metro station chosen
    Mayapuri metro station is a station on the Delhi Metro network serving the Mayapuri industrial and residential area in West Delhi.
  • B. Chaitanyapuri metro station
    Chaitanyapuri metro station is an elevated station on Hyderabad Metro serving the Chaitanyapuri area in the city’s eastern corridor.
  • C. Vaishali metro station
    Vaishali metro station is a key Delhi Metro terminal station serving commuters in the Ghaziabad region of the National Capital Region.
  • D. Govindpuri metro station
    Govindpuri metro station is a station on Delhi Metro’s Violet Line serving the Govindpuri and surrounding South Delhi residential and commercial areas.
  • E. Lakdi-ka-pul metro station
    Lakdi-ka-pul metro station is an elevated station on the Hyderabad Metro system serving the busy Lakdi-ka-pul area near central Hyderabad.
  • 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_69e0b512ad94819087942b2ed925185f completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734b1524c8190a77eaf2fabd601c3 completed April 21, 2026, 8:26 a.m.
Created at: April 16, 2026, 3:45 p.m.