Triple

T12554898
Position Surface form Disambiguated ID Type / Status
Subject Bhumij E295188 entity
Predicate language P15 FINISHED
Object Bhumij language E734616 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: Bhumij language | Statement: [Bhumij, language, Bhumij language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bhumij language
Context triple: [Bhumij, language, Bhumij language]
  • A. Bhumij language chosen
    Bhumij language is an Austroasiatic language of the Munda family spoken primarily by the Bhumij people in eastern India.
  • B. Khumi language
    The Khumi language is a lesser-known Tibeto-Burman language spoken primarily by the Khumi people in parts of Myanmar and neighboring regions.
  • C. Chumburung language
    The Chumburung language is a Niger-Congo language spoken primarily by the Chumburung people in Ghana.
  • D. Gumer language
    The Gumer language is an Afroasiatic Semitic language spoken by the Gumer people of the Gurage region in central Ethiopia.
  • E. Blablanga language
    The Blablanga language is an Oceanic language spoken in the Solomon Islands, belonging to the Northwest Solomonic subgroup of the Austronesian language family.
  • 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_69d6ad9cac2c81908e8a7bed82d1e21d completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d95490d2708190857f0cb9b8dd6a30 completed April 10, 2026, 7:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f65587524881908c933490bface976 completed May 2, 2026, 7:50 p.m.
Created at: April 8, 2026, 11:45 p.m.