Triple

T19099373
Position Surface form Disambiguated ID Type / Status
Subject Keslapur Jathra E467487 entity
Predicate languageContext P36 FINISHED
Object Gondi 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: Gondi language | Statement: [Keslapur Jathra, languageContext, Gondi language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gondi language
Context triple: [Keslapur Jathra, languageContext, Gondi language]
  • A. Gondi language chosen
    The Gondi language is a Dravidian language spoken by the indigenous Gond people of central India, written in multiple scripts including Telugu and Devanagari.
  • B. Kumaoni language
    Kumaoni language is an Indo-Aryan language of the Central Pahari group spoken primarily in the Kumaon region of Uttarakhand, India.
  • C. Mofu-Gudur language
    The Mofu-Gudur language is a Central Chadic language spoken primarily by the Mofu-Gudur people in northern Cameroon.
  • D. Gondi–Kui languages
    The Gondi–Kui languages are a branch of the Dravidian language family spoken primarily by tribal communities in central and eastern India, including languages such as Gondi and Kui.
  • E. Gonja language
    The Gonja language is a Gur language spoken primarily by the Gonja people in northern Ghana.
  • 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_69d8dd05ac4c8190b1967d8f97f3fb2f completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e36c55688190b4a5135ea10c9924 completed April 20, 2026, 8:27 a.m.
Created at: April 10, 2026, 12:04 p.m.