Triple

T18934703
Position Surface form Disambiguated ID Type / Status
Subject Noida Sector 76 E463211 entity
Predicate metroSystem P32065 FINISHED
Object Noida 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: Noida Metro | Statement: [Noida Sector 76, metroSystem, Noida Metro]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Noida Metro
Context triple: [Noida Sector 76, metroSystem, Noida Metro]
  • A. Noida Metro chosen
    Noida Metro is a rapid transit system serving the city of Noida and its surrounding areas in India’s National Capital Region.
  • B. Delhi Metro
    Delhi Metro is a rapid transit system serving Delhi and its surrounding metropolitan region, known for its extensive network, modern infrastructure, and role in easing urban congestion.
  • C. Lucknow Metro
    Lucknow Metro is a rapid transit system serving the city of Lucknow in Uttar Pradesh, India, designed to provide fast, modern urban transportation.
  • D. Rapid Metro Gurgaon
    Rapid Metro Gurgaon is a privately built and operated light rapid transit system serving key commercial and residential areas of Gurugram in the National Capital Region of India.
  • E. 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.
  • 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_69d8dcfec90481909e926be9767e5779 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d3e6a8208190973669cae439a91e completed April 20, 2026, 7:21 a.m.
Created at: April 10, 2026, 11:59 a.m.