Triple

T22930677
Position Surface form Disambiguated ID Type / Status
Subject Hingoli district E569427 entity
Predicate headquarters P62 FINISHED
Object Hingoli 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: Hingoli | Statement: [Hingoli district, headquarters, Hingoli]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hingoli
Context triple: [Hingoli district, headquarters, Hingoli]
  • A. Hingoli chosen
    Hingoli is a city in the Indian state of Maharashtra, known as an administrative and commercial center in the Marathwada region.
  • B. Buldhana
    Buldhana is a district in the Indian state of Maharashtra known for its Marathi-speaking population and use of the Varhadi dialect.
  • C. Sangli
    Sangli is a city in the Indian state of Maharashtra known for its fertile agricultural surroundings and prominence in sugar and turmeric production.
  • D. Ratnagiri
    Ratnagiri is a coastal city in Maharashtra, India, known for its Alphonso mangoes, historic forts, and scenic beaches along the Konkan coast.
  • E. Latur
    Latur is a city in the Marathwada region of western India known for its agricultural economy and for being the epicenter of a devastating earthquake in 1993.
  • 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_69e2458f7d008190901dccbaebeaba24 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18131956c8190b8c850fc1d57a119 completed April 29, 2026, 3:55 a.m.
Created at: April 17, 2026, 3:44 p.m.