Triple

T939344
Position Surface form Disambiguated ID Type / Status
Subject Gondi E20268 entity
Predicate hasDialects P4251 FINISHED
Object Muria Gondi E113044 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: Muria Gondi | Statement: [Gondi, hasDialects, Muria Gondi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Muria Gondi
Context triple: [Gondi, hasDialects, Muria Gondi]
  • A. Bhonsle
    The Bhonsle were a prominent Maratha royal dynasty best known for producing Chhatrapati Shivaji, founder of the Maratha Empire in western India.
  • B. Guna
    Guna is a city in the central Indian state of Madhya Pradesh known as an important regional administrative and commercial center.
  • C. Sardeshmukhi
    Sardeshmukhi was a tax levied by the Maratha Empire, typically an additional surcharge claimed by Maratha rulers over and above regular land revenue in territories under their influence.
  • D. Dhundhari
    Dhundhari is an Indo-Aryan language spoken primarily in and around Jaipur and adjoining regions of Rajasthan, India.
  • E. Dorla Gondi chosen
    Dorla Gondi is a regional dialect of the Gondi language spoken by the Dorla subgroup of the Gondi people in central India.
  • 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_69a493b0270c81909e6c9ce310f6aa55 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b38a3ad4819080d71849e822a12a completed March 1, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac4c017e148190b368419cff3872f6 completed March 7, 2026, 4:02 p.m.
Created at: March 1, 2026, 7:40 p.m.