Triple

T17103379
Position Surface form Disambiguated ID Type / Status
Subject Mbuzini, South Africa E415034 entity
Predicate hasLanguage P15 FINISHED
Object Xitsonga E25191 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: Xitsonga | Statement: [Mbuzini, South Africa, hasLanguage, Xitsonga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Xitsonga
Context triple: [Mbuzini, South Africa, hasLanguage, Xitsonga]
  • A. Xitsonga chosen
    Xitsonga is a Bantu language spoken primarily by the Tsonga people in southern Africa, notably in South Africa, Mozambique, and Zimbabwe.
  • B. Siswati
    Siswati is a Bantu language of the Nguni group spoken primarily in Eswatini and South Africa, where it holds official status.
  • C. Tshivenda
    Tshivenda is a Bantu language spoken primarily by the Venda people in northern South Africa and neighboring regions.
  • D. Xhosa
    Xhosa is a Bantu language of South Africa, known for its distinctive click consonants and as one of the country’s major official languages.
  • E. Setswana
    Setswana is a Bantu language spoken primarily in Botswana and parts of South Africa, known for being one of the region’s major indigenous languages.
  • 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_69d886cfc8e88190b05ba466edd35591 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dc2495c88190b5b16a006a994faf completed April 18, 2026, 7:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0139ffbe808190a24e827331ee4a6c completed May 11, 2026, 2:07 a.m.
Created at: April 10, 2026, 5:35 a.m.