Triple

T6980669
Position Surface form Disambiguated ID Type / Status
Subject Mhow E161834 entity
Predicate formerName P65 FINISHED
Object Mhow Cantonment E161834 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: Mhow Cantonment | Statement: [Mhow, formerName, Mhow Cantonment]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mhow Cantonment
Context triple: [Mhow, formerName, Mhow Cantonment]
  • A. Gwalior Cantonment
    Gwalior Cantonment is a major Indian Army military station located in the city of Gwalior in Madhya Pradesh.
  • B. Jabalpur Cantonment
    Jabalpur Cantonment is a major Indian Army cantonment area located in the city of Jabalpur in central India.
  • C. Agra Cantonment
    Agra Cantonment is a major Indian Army military station and the primary railway hub of Agra, Uttar Pradesh.
  • D. Mhow chosen
    Mhow is a cantonment town in the Indore district of Madhya Pradesh, India, historically significant as a British-era military base and now known as Dr. Ambedkar Nagar.
  • E. Ambala Cantonment
    Ambala Cantonment is a prominent military and commercial town in Haryana, India, known for its strategic location and major railway junction.
  • 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_69c68855dc0481909b4c7e9e9ed273db completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6db6c1efc8190ab1575ae2ce726db completed March 27, 2026, 7:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69c761c0ecd88190a684392aa6daf267 completed March 28, 2026, 5:06 a.m.
Created at: March 27, 2026, 2:31 p.m.