Triple

T5060232
Position Surface form Disambiguated ID Type / Status
Subject Vidarbha E114004 entity
Predicate hasMajorCity 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: [Vidarbha, hasMajorCity, Buldhana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Buldhana
Context triple: [Vidarbha, hasMajorCity, 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. Ratnagiri
    Ratnagiri is a coastal city in Maharashtra, India, known for its Alphonso mangoes, historic forts, and scenic beaches along the Konkan coast.
  • 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. Baramati
    Baramati is a town in the Pune district of Maharashtra, India, known as an agricultural and industrial hub with historical and political significance.
  • 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 (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_69bd443c0c8c81908663b77afb28e165 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd7472a1dc8190942f568a81fdd961 completed March 20, 2026, 4:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69beb102bb348190b235e4adb7a3f88b completed March 21, 2026, 2:53 p.m.
Created at: March 20, 2026, 1:38 p.m.