Triple

T22376336
Position Surface form Disambiguated ID Type / Status
Subject Ganjami E553159 entity
Predicate hasAlternativeName P39 FINISHED
Object Ganjami Odia 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: Ganjami Odia | Statement: [Ganjami, hasAlternativeName, Ganjami Odia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ganjami Odia
Context triple: [Ganjami, hasAlternativeName, Ganjami Odia]
  • A. Ganjami Odia chosen
    Ganjami Odia is a regional variety of the Odia language spoken primarily in the Ganjam region of Odisha, India, characterized by distinct phonetic and lexical features.
  • B. Ganjami
    Ganjami is a regional dialect of the Odia language spoken primarily in the Ganjam region of Odisha, India.
  • C. Maithili
    Maithili is an Indo-Aryan language spoken primarily in the eastern Indian state of Bihar and neighboring regions, with a rich literary tradition and official recognition in India.
  • D. 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.
  • E. Bhuyan Odia
    Bhuyan Odia is a regional dialect of the Odia language spoken by the Bhuyan community in parts of eastern 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.