Triple

T22966465
Position Surface form Disambiguated ID Type / Status
Subject Bamoun E571059 entity
Predicate language P15 FINISHED
Object Bamun 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: Bamun language | Statement: [Bamoun, language, Bamun language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bamun language
Context triple: [Bamoun, language, Bamun language]
  • A. Bamun language group chosen
    The Bamun language group is a subgroup of the Grassfields Bantu languages spoken primarily by the Bamun people in western Cameroon.
  • B. Bambam language
    The Bambam language is an Austronesian language spoken in parts of South Sulawesi, Indonesia, known for its place within the region’s diverse indigenous linguistic landscape.
  • C. Bitama language
    The Bitama language is a lesser-known Nilo-Saharan language spoken by a subgroup of the Kunama people in the Horn of Africa.
  • D. Mangbetu language
    The Mangbetu language is a Central Sudanic language spoken by the Mangbetu people of northeastern Democratic Republic of the Congo.
  • E. Munji language
    The Munji language is an Eastern Iranian language spoken by the Munji people in Afghanistan’s remote Munjan Valley, closely related to the Yidgha language of Pakistan.
  • 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_69e245b2c6548190a0e4c7f2f7df2d48 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1822f57088190addc6857063b4cca completed April 29, 2026, 3:59 a.m.
Created at: April 17, 2026, 3:47 p.m.