Triple

T17378174
Position Surface form Disambiguated ID Type / Status
Subject Agra–Delhi chord E422494 entity
Predicate servesCity P82 FINISHED
Object Delhi Cantonment 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 Cantonment | Statement: [Agra–Delhi chord, servesCity, Delhi Cantonment]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Delhi Cantonment
Context triple: [Agra–Delhi chord, servesCity, Delhi Cantonment]
  • A. Delhi Cantonment chosen
    Delhi Cantonment is a prominent military area in New Delhi that serves as a major base and administrative center for the Indian Armed Forces.
  • B. Meerut Cantonment
    Meerut Cantonment is a prominent military cantonment area and residential suburb in the city of Meerut, Uttar Pradesh, India.
  • C. Agra Cantonment
    Agra Cantonment is a major Indian Army military station and the primary railway hub of Agra, Uttar Pradesh.
  • D. Ambala Cantonment
    Ambala Cantonment is a prominent military and commercial town in Haryana, India, known for its strategic location and major railway junction.
  • E. Lucknow Cantonment
    Lucknow Cantonment is a prominent military and residential area in Lucknow, Uttar Pradesh, known for its army establishments, orderly infrastructure, and role as a state legislative assembly constituency.
  • 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_69d889d6535c81908be333c01deaec4e completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e43a6ea56c8190b56d966ccf2c91f7 completed April 19, 2026, 2:14 a.m.
Created at: April 10, 2026, 5:45 a.m.