Triple

T20638038
Position Surface form Disambiguated ID Type / Status
Subject Ujjain district E507137 entity
Predicate containsTown P847 FINISHED
Object Mahidpur 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: Mahidpur | Statement: [Ujjain district, containsTown, Mahidpur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mahidpur
Context triple: [Ujjain district, containsTown, Mahidpur]
  • A. Mahidpur chosen
    Mahidpur is a historic town in the Indian state of Madhya Pradesh, known for its location in the Malwa region and its role in the Anglo-Maratha conflicts.
  • B. Rampurhat
    Rampurhat is a town and important railway junction in the Birbhum district of West Bengal, India.
  • C. Santipur
    Santipur is a historic town in West Bengal, India, renowned for its traditional handloom sarees and cultural heritage.
  • D. Shibpur
    Shibpur is a prominent residential and institutional neighborhood in Howrah, West Bengal, known for landmarks like the Indian Institute of Engineering Science and Technology and the Acharya Jagadish Chandra Bose Indian Botanic Garden.
  • E. Kumarghat
    Kumarghat is a town in the Indian state of Tripura, known as a local commercial and transport hub in the Unakoti district.
  • 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_69e0b4be702c8190a3d2410a881d310a completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6ad1163008190aa9df36750a952d2 completed April 20, 2026, 10:47 p.m.
Created at: April 16, 2026, 11:42 a.m.