Triple

T16221751
Position Surface form Disambiguated ID Type / Status
Subject Kolo E393742 entity
Predicate closelyRelatedTo P37 FINISHED
Object Bulu language E87000 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: Bulu language | Statement: [Kolo, closelyRelatedTo, Bulu language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bulu language
Context triple: [Kolo, closelyRelatedTo, Bulu language]
  • A. Bulu language chosen
    The Bulu language is a Bantu language spoken primarily in southern Cameroon, closely associated with the Beti-Pahuin peoples and used historically in education and Christian missions.
  • B. Buli language
    Buli is an Austronesian language spoken on Halmahera Island in eastern Indonesia, known for its complex verbal morphology and membership in the South Halmahera–West New Guinea subgroup.
  • C. Buli language
    Buli is a Gur language spoken primarily in northern Ghana by the Builsa (Buli) people.
  • D. Bulungan language
    The Bulungan language is an Austronesian language spoken by the Bulungan people of northern Borneo, particularly in Indonesia’s North Kalimantan region.
  • E. Bulang language
    The Bulang language is a Mon–Khmer language spoken primarily by the Bulang ethnic group in parts of Yunnan, China.
  • 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_69d87f204df88190a8f88923decf9835 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e227fcf058819099d5ff965cc2c267 completed April 17, 2026, 12:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00079a5c1481909485e1b4a41f5d2c completed May 10, 2026, 4:20 a.m.
Created at: April 10, 2026, 5:03 a.m.