Triple

T22139710
Position Surface form Disambiguated ID Type / Status
Subject Hlubi E547123 entity
Predicate relatedEthnicGroup P1969 FINISHED
Object Xhosa 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: Xhosa | Statement: [Hlubi, relatedEthnicGroup, Xhosa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Xhosa
Context triple: [Hlubi, relatedEthnicGroup, Xhosa]
  • A. Xhosa chosen
    Xhosa is a Bantu language of South Africa, known for its distinctive click consonants and as one of the country’s major official languages.
  • B. Siswati
    Siswati is a Bantu language of the Nguni group spoken primarily in Eswatini and South Africa, where it holds official status.
  • C. Xitsonga
    Xitsonga is a Bantu language spoken primarily by the Tsonga people in southern Africa, notably in South Africa, Mozambique, and Zimbabwe.
  • D. Tshivenda
    Tshivenda is a Bantu language spoken primarily by the Venda people in northern South Africa and neighboring regions.
  • E. Zulu
    Zulu is a Bantu language of the Nguni group spoken primarily in South Africa and widely influential in the country’s culture and other local languages.
  • 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_69e11e3a95d88190a3bd80d9471976c3 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f129bda1208190b851ae5c68b760e9 completed April 28, 2026, 9:42 p.m.
Created at: April 16, 2026, 8:32 p.m.