Triple

T12789078
Position Surface form Disambiguated ID Type / Status
Subject Berar E305708 entity
Predicate majorCity P316 FINISHED
Object Buldhana E182083 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: Buldhana | Statement: [Berar, majorCity, Buldhana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Buldhana
Context triple: [Berar, majorCity, Buldhana]
  • A. Buldhana chosen
    Buldhana is a district in the Indian state of Maharashtra known for its Marathi-speaking population and use of the Varhadi dialect.
  • B. Hingoli
    Hingoli is a city in the Indian state of Maharashtra, known as an administrative and commercial center in the Marathwada region.
  • C. Ratnagiri
    Ratnagiri is a coastal city in Maharashtra, India, known for its Alphonso mangoes, historic forts, and scenic beaches along the Konkan coast.
  • D. Bhusawal
    Bhusawal is a major railway and commercial city in Maharashtra, India, known for its large railway junction and banana-growing region.
  • E. Malegaon
    Malegaon is a major textile and powerloom town in Maharashtra, India, known for its large Muslim population and vibrant weaving industry.
  • 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_69d7bdf366888190a8cccb982606889c completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96e6a61f48190972e241e70bc392c completed April 10, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f68ebeab2081908a6e38351613e3ed completed May 2, 2026, 11:54 p.m.
Created at: April 9, 2026, 5:30 p.m.