Triple

T11377744
Position Surface form Disambiguated ID Type / Status
Subject Maheshwar E269512 entity
Predicate locatedNear P294 FINISHED
Object Khargone E151925 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: Khargone | Statement: [Maheshwar, locatedNear, Khargone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khargone
Context triple: [Maheshwar, locatedNear, Khargone]
  • A. Khargone chosen
    Khargone is a city in western Madhya Pradesh, India, known as an agricultural and commercial center in the Nimar region.
  • B. Jhabua
    Jhabua is a town and administrative district headquarters in western Madhya Pradesh, India, known for its significant tribal population and culture.
  • C. Hoshangabad
    Hoshangabad is a city in the Indian state of Madhya Pradesh, known for its location on the banks of the Narmada River and its agricultural and industrial activities.
  • D. Kharadi
    Kharadi is a rapidly developing suburb in Pune, India, known as a major IT and business hub with modern infrastructure and residential complexes.
  • E. Wadhwan
    Wadhwan is a historic town in Gujarat, India, known for its royal heritage, old fortifications, and role as a former princely state center.
  • 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_69d6aacca1048190b39dbbc2174616fa completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7fc30f5d48190bb273df4c9e583a9 completed April 9, 2026, 7:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69e58bff6574819089bd63266b97a734 completed April 20, 2026, 2:14 a.m.
Created at: April 8, 2026, 9:33 p.m.