Triple

T22376329
Position Surface form Disambiguated ID Type / Status
Subject Ganjami E553159 entity
Predicate partOfLanguage P46016 FINISHED
Object Odia 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: Odia language | Statement: [Ganjami, partOfLanguage, Odia language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Odia language
Context triple: [Ganjami, partOfLanguage, Odia language]
  • A. Odia chosen
    Odia is an Indo-Aryan language spoken primarily in the Indian state of Odisha, known for its rich literary tradition and classical language status.
  • B. Sansibari language
    The Sansibari language is a lesser-known Western Indo-Aryan language historically spoken by South Asian communities in Zanzibar and nearby regions of East Africa.
  • C. Santhali
    Santhali is an Austroasiatic language spoken primarily by the Santal people in eastern India, Bangladesh, Nepal, and Bhutan.
  • D. Birhor language
    Birhor language is an endangered Munda language of the Austroasiatic family spoken by the Birhor indigenous community in eastern India.
  • E. Bastar Gondi
    Bastar Gondi is a regional variety of the Gondi language spoken primarily by the Gond people in the Bastar region of central 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_69e11e4c03248190a26a5060ea6973ee completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f158285d208190bc7d05d315267995 completed April 29, 2026, 1 a.m.
Created at: April 16, 2026, 8:45 p.m.