Triple

T5895708
Position Surface form Disambiguated ID Type / Status
Subject Baleswari Odia E131095 entity
Predicate hasAncestor P369 FINISHED
Object Odia language E24420 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: Odia language | Statement: [Baleswari Odia, hasAncestor, Odia language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Odia language
Context triple: [Baleswari Odia, hasAncestor, 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. Santhali
    Santhali is an Austroasiatic language spoken primarily by the Santal people in eastern India, Bangladesh, Nepal, and Bhutan.
  • C. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • D. Mundari
    Mundari is an Austroasiatic Munda language of eastern India, spoken primarily by the Munda people in states such as Jharkhand, Odisha, and West Bengal.
  • E. Kharia language
    Kharia language is a Munda language spoken primarily by the Kharia people in eastern India, especially in the states of Jharkhand, Odisha, and Chhattisgarh.
  • 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_69c00857439c819095950754176aa58a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c036f3364c81909353f62ca483f24f completed March 22, 2026, 6:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69c108039acc8190a5ce23412f1a359c completed March 23, 2026, 9:29 a.m.
Created at: March 22, 2026, 3:58 p.m.