Triple

T8034771
Position Surface form Disambiguated ID Type / Status
Subject Violet Line E187077 entity
Predicate system P730 FINISHED
Object Delhi Metro E19472 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: Delhi Metro | Statement: [Violet Line, system, Delhi Metro]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Delhi Metro
Context triple: [Violet Line, system, Delhi Metro]
  • A. Delhi Metro chosen
    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.
  • B. Noida Metro
    Noida Metro is a rapid transit system serving the city of Noida and its surrounding areas in India’s National Capital Region.
  • C. 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.
  • D. Red Line (Delhi Metro)
    Red Line (Delhi Metro) is one of the major lines of the Delhi Metro network, serving the northern and eastern parts of Delhi and extending into neighboring regions.
  • E. Kolkata Metro
    Kolkata Metro is India’s oldest rapid transit system, serving as a major urban rail network for the city of Kolkata and its surrounding areas.
  • 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_69ca82ae2d1081909dbfee42b41db419 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3ef50f4c8190a895ac301f182734 completed March 31, 2026, 3:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69ce01e53c4c81908cef500bc7f82b1c completed April 2, 2026, 5:43 a.m.
Created at: March 30, 2026, 5:22 p.m.