Triple

T15324363
Position Surface form Disambiguated ID Type / Status
Subject Hambukushu people E366370 entity
Predicate hasEndonym P1435 FINISHED
Object Mbukushu E1078473 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: Mbukushu | Statement: [Hambukushu people, hasEndonym, Mbukushu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mbukushu
Context triple: [Hambukushu people, hasEndonym, Mbukushu]
  • A. Mbukushu chosen
    Mbukushu is a Bantu language spoken by the Mbukushu people primarily in northeastern Namibia and neighboring regions of Botswana and Angola.
  • B. Mkushi
    Mkushi is a farming and trading town in Zambia known for its commercial agriculture, particularly large-scale commercial farming.
  • C. Mzuzu
    Mzuzu is a major city in northern Malawi known as an important commercial and administrative center for the region.
  • D. Mberengwa
    Mberengwa is a rural district and growth point in Zimbabwe known for its mining activities and location in the southern part of the Midlands Province.
  • E. Mankwe
    Mankwe is a locality in South Africa, historically part of the former Bophuthatswana homeland in the North West Province.
  • 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_69d85a121520819093dcce999fdefe1a completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03dd5ce0c819093c9a14de549dff6 completed April 16, 2026, 1:39 a.m.
NED1 Entity disambiguation (via context triple) batch_69fef8aaef608190bd3ec9fdd215afbb completed May 9, 2026, 9:04 a.m.
Created at: April 10, 2026, 3:16 a.m.