Triple

T10070105
Position Surface form Disambiguated ID Type / Status
Subject Bhavra E213598 entity
Predicate hasRegionalLanguage P2982 FINISHED
Object Bhili E460693 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: Bhili | Statement: [Bhavra, hasRegionalLanguage, Bhili]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bhili
Context triple: [Bhavra, hasRegionalLanguage, Bhili]
  • A. Bhili chosen
    Bhili is an Indo-Aryan language spoken primarily by the Bhil tribal communities in western and central India.
  • B. Bhailsa
    Bhailsa is the former historical name of Vidisha, an ancient city in the central Indian state of Madhya Pradesh known for its rich archaeological and cultural heritage.
  • C. Dhundhari
    Dhundhari is an Indo-Aryan language spoken primarily in and around Jaipur and adjoining regions of Rajasthan, India.
  • D. Bantawa Rai
    Bantawa Rai are a subgroup of the Rai people of eastern Nepal, known for their distinct Bantawa language and rich Kirati cultural traditions.
  • E. Kondh
    The Kondh are an indigenous tribal community of eastern India, particularly Odisha, known for their distinct Kui language, traditional agrarian lifestyle, and rich ritual and festival practices.
  • 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_69ca839add308190b57d53b4ec21f2d0 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cdcffa045c8190a08db0bb74cb006a completed April 2, 2026, 2:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69d29aa05cc881909f59178e9c6c01ef completed April 5, 2026, 5:23 p.m.
Created at: March 30, 2026, 8:58 p.m.