Triple

T20170623
Position Surface form Disambiguated ID Type / Status
Subject East Nimar E491947 entity
Predicate railwayJunctionAt P36754 FINISHED
Object Khandwa 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: Khandwa | Statement: [East Nimar, railwayJunctionAt, Khandwa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khandwa
Context triple: [East Nimar, railwayJunctionAt, Khandwa]
  • A. Khandwa chosen
    Khandwa is a city in central India known as a regional commercial and cultural center in the state of Madhya Pradesh.
  • B. Jambusar
    Jambusar is a town in the Bharuch district of Gujarat, India, known for its historical significance and regional trade and agriculture.
  • C. Dantiwada
    Dantiwada is a small town in Gujarat, India, known primarily for its agricultural university and proximity to the Dantiwada Dam in Banaskantha district.
  • D. Jhabua
    Jhabua is a town and administrative district headquarters in western Madhya Pradesh, India, known for its significant tribal population and culture.
  • E. Chandkheda
    Chandkheda is a residential and industrial locality in the northwestern part of Ahmedabad, Gujarat, known for its proximity to major infrastructure and educational institutions.
  • 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_69da6266c6888190bc1a3ecf24814d34 completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e66847ed9481908e6b23b399fa7005 completed April 20, 2026, 5:54 p.m.
Created at: April 11, 2026, 11:35 p.m.