Triple

T20081484
Position Surface form Disambiguated ID Type / Status
Subject Bhind Municipal Council E500011 entity
Predicate locatedIn P40 FINISHED
Object Bhind 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: Bhind | Statement: [Bhind Municipal Council, locatedIn, Bhind]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bhind
Context triple: [Bhind Municipal Council, locatedIn, Bhind]
  • A. Bhind chosen
    Bhind is a city in the northern part of the Indian state of Madhya Pradesh, known as an administrative and commercial center of the region.
  • B. Bijbehara
    Bijbehara is a historic town in the Kashmir Valley of Jammu and Kashmir, India, known for its apple orchards and scenic location along the Jhelum River.
  • C. Sonipat
    Sonipat is a rapidly developing city in the northern Indian state of Haryana that forms part of the extended urban and economic area around Delhi.
  • D. Shivpuri
    Shivpuri is a historic town and former princely state in central India, known for its forests, wildlife sanctuaries, and royal palaces.
  • E. Karauli
    Karauli is a historic town and pilgrimage center in the Indian state of Rajasthan, known for its ancient temples and distinctive red sandstone architecture.
  • 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_69da627770948190997f486f9a2e370f completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66557c19c8190b511857490bbd423 completed April 20, 2026, 5:41 p.m.
Created at: April 11, 2026, 3:41 p.m.