Triple

T10761148
Position Surface form Disambiguated ID Type / Status
Subject Madhepura district E253828 entity
Predicate headquarters P62 FINISHED
Object Madhepura E316642 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: Madhepura | Statement: [Madhepura district, headquarters, Madhepura]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Madhepura
Context triple: [Madhepura district, headquarters, Madhepura]
  • A. Madhepura chosen
    Madhepura is a town and district headquarters in the eastern Indian state of Bihar, known for its agricultural economy and regional administrative importance.
  • B. Pratapgarh
    Pratapgarh is a town in the Indian state of Rajasthan known for its historical association with the Mewar region and its distinctive tribal culture and handicrafts.
  • C. Anuppur
    Anuppur is a town and administrative district headquarters in the central Indian state of Madhya Pradesh, known for its proximity to coal mining areas and natural attractions.
  • D. Dholpur
    Dholpur is a city in the Indian state of Rajasthan, known for its red sandstone, historical forts, and location near the Chambal ravines.
  • E. Purnia
    Purnia is a major city in northeastern India known as a commercial and agricultural hub of the Seemanchal region.
  • 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_69d6aa5f54f4819082d0bbcb6f8797e6 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d731a230ac8190920439076aaeb91e completed April 9, 2026, 4:57 a.m.
NED1 Entity disambiguation (via context triple) batch_69e3e6d27d8c8190b2c8ee9c54cf7fd1 completed April 18, 2026, 8:17 p.m.
Created at: April 8, 2026, 9:16 p.m.