Triple

T21454813
Position Surface form Disambiguated ID Type / Status
Subject Bhili–Khandeshi subgroup E529313 entity
Predicate hasMember P10 FINISHED
Object Dhanka language 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: Dhanka language | Statement: [Bhili–Khandeshi subgroup, hasMember, Dhanka language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dhanka language
Context triple: [Bhili–Khandeshi subgroup, hasMember, Dhanka language]
  • A. Dhanka language chosen
    Dhanka is an Indo-Aryan tribal language variety considered a dialect within the Bhili language group of western India.
  • B. Dhatki language
    Dhatki language is an Indo-Aryan language spoken primarily by the Thari people in the Thar Desert region spanning parts of Pakistan and India.
  • C. Dhundari language
    The Dhundari language is an Indo-Aryan language spoken primarily in the Indian state of Rajasthan, closely associated with the Rajasthani dialect continuum.
  • D. Dhurga language
    The Dhurga language is an Australian Aboriginal language traditionally spoken by the Yuin people of the south coast of New South Wales.
  • E. Kumaoni language
    Kumaoni language is an Indo-Aryan language of the Central Pahari group spoken primarily in the Kumaon region of Uttarakhand, India.
  • 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_69e0c457579481909db68053ed99750c completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9e9d612e081909d00ca59a3621cc9 completed April 23, 2026, 9:43 a.m.
Created at: April 16, 2026, 6:08 p.m.