Triple

T6678849
Position Surface form Disambiguated ID Type / Status
Subject Khargone E151925 entity
Predicate connectedTo P37 FINISHED
Object Khandwa E114390 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: Khandwa | Statement: [Khargone, connectedTo, Khandwa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khandwa
Context triple: [Khargone, connectedTo, 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. Jhabua
    Jhabua is a town and administrative district headquarters in western Madhya Pradesh, India, known for its significant tribal population and culture.
  • C. Ratlam
    Ratlam is a prominent commercial city in western Madhya Pradesh, India, known for its railway junction, textile and chemical industries, and production of gold and silver jewelry.
  • D. Dhrol
    Dhrol is a town in the Jamnagar district of Gujarat, India, known historically as the seat of the former princely Dhrol State.
  • E. Marvadi
    Marvadi is an alternative name for the Marwari people and their Indo-Aryan language traditionally associated with the Marwar region of Rajasthan, India.
  • 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_69c687f830bc81909eb8b04dbb8450b1 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6b0f6813c8190906f619b4276a232 completed March 27, 2026, 4:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69c71a6a2c008190bc926b5d095c3ca9 completed March 28, 2026, 12:01 a.m.
Created at: March 27, 2026, 2:03 p.m.