Triple

T17671012
Position Surface form Disambiguated ID Type / Status
Subject Mula Dam E440519 entity
Predicate regionServed P82 FINISHED
Object Newasa taluka 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: Newasa taluka | Statement: [Mula Dam, regionServed, Newasa taluka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Newasa taluka
Context triple: [Mula Dam, regionServed, Newasa taluka]
  • A. Nevasa taluka chosen
    Nevasa taluka is an administrative sub-division in Ahmednagar district of Maharashtra, India, known for its agricultural landscape and local governance role.
  • B. Rahata taluka
    Rahata taluka is an administrative sub-division in Ahmednagar district of Maharashtra, India, known for encompassing the pilgrimage town of Shirdi.
  • C. Olpad taluka
    Olpad taluka is an administrative subdivision in the coastal region of Gujarat, India, falling under Surat district and known for its rural settlements and salt-pan industries.
  • D. Haveli taluka
    Haveli taluka is an administrative subdivision in Pune district of Maharashtra, India, encompassing both urban and rural areas around the city of Pune.
  • E. Mahuva taluka
    Mahuva taluka is an administrative sub-division (taluka) in the Surat district of the Indian state of Gujarat.
  • 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_69d8b9e87e18819087104a44dc4dc5b1 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e46f68a038819084828ff73bcf1fcc completed April 19, 2026, 6 a.m.
Created at: April 10, 2026, 9:59 a.m.