Triple

T18436549
Position Surface form Disambiguated ID Type / Status
Subject Delhi–Amritsar line E450406 entity
Predicate majorStation P1071 FINISHED
Object Delhi Junction 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: Delhi Junction | Statement: [Delhi–Amritsar line, majorStation, Delhi Junction]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Delhi Junction
Context triple: [Delhi–Amritsar line, majorStation, Delhi Junction]
  • A. Delhi Jn chosen
    Delhi Jn is a major historic railway junction in Old Delhi that serves as one of the busiest and oldest rail hubs in India.
  • B. Chirag Delhi
    Chirag Delhi is a historic urban village and residential neighborhood located in the South Delhi district of India’s capital, New Delhi.
  • C. Delhi
    Delhi is a major metropolitan region and the capital territory of India, known for its political significance, rich history, and diverse culture.
  • D. INS Delhi
    INS Delhi is an Indian Navy guided-missile destroyer that originally served in the Royal Navy as HMS Achilles before being transferred and renamed.
  • E. Mumbai Central
    Mumbai Central is a major railway terminus in Mumbai, India, serving as a key hub for long-distance and suburban train services on the Western 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_69d8d381d6388190a9e94e9c658174e4 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e51c0cd30c8190b8417c264e60d3a5 completed April 19, 2026, 6:16 p.m.
Created at: April 10, 2026, 11:29 a.m.