Triple

T20099703
Position Surface form Disambiguated ID Type / Status
Subject Kaimur district E496500 entity
Predicate headquarters P62 FINISHED
Object Bhabua E1135007 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: Bhabua | Statement: [Kaimur district, headquarters, Bhabua]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bhabua
Context triple: [Kaimur district, headquarters, Bhabua]
  • A. Bhabua chosen
    Bhabua is a town in the Indian state of Bihar that serves as the headquarters of Kaimur district.
  • B. Bhatarka
    Bhatarka was an early Indian ruler who founded the Maitraka dynasty, establishing its power base in the region of present-day Gujarat.
  • C. Naihati
    Naihati is a town in West Bengal, India, known as the birthplace of renowned Bengali novelist and nationalist Bankim Chandra Chattopadhyay.
  • D. Birpur
    Birpur is a town in the Supaul district of Bihar, India, situated near the Kosi River and known for its proximity to the major Kosi Barrage.
  • E. Chakulia
    Chakulia is a town in Jharkhand, India, known as an emerging urban and industrial hub within the greater Jamshedpur industrial 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_69da626eee3881909f3454986d4a6511 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6666f2298819089659f13556ca305 completed April 20, 2026, 5:46 p.m.
NED1 Entity disambiguation (via context triple) batch_6a08270edd6481909230ece4487f93fd completed May 16, 2026, 8:13 a.m.
Created at: April 11, 2026, 11:26 p.m.