Triple

T5158308
Position Surface form Disambiguated ID Type / Status
Subject Shashe River E116368 entity
Predicate languageOfName P15 FINISHED
Object Tswana E24414 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: Tswana | Statement: [Shashe River, languageOfName, Tswana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tswana
Context triple: [Shashe River, languageOfName, Tswana]
  • A. Setswana chosen
    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.
  • B. Sotho
    Sotho is a Bantu language of Southern Africa, primarily spoken in Lesotho and South Africa, where it serves as one of the country’s official languages.
  • C. Sotho–Tswana languages
    The Sotho–Tswana languages are a closely related group of Southern Bantu languages spoken primarily in South Africa, Lesotho, and Botswana, including Sesotho, Setswana, and Sepedi.
  • D. Sesotho
    Sesotho is a Southern Bantu language spoken primarily in Lesotho and South Africa, where it holds official status and serves as a major medium of communication and cultural identity.
  • E. Tshivenda
    Tshivenda is a Bantu language spoken primarily by the Venda people in northern South Africa and neighboring regions.
  • 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_69bd445d94788190b72e2cc563120995 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7904457c819090f382029ebb2b43 completed March 20, 2026, 4:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69bed01a85f88190827a79a2c26e539f completed March 21, 2026, 5:06 p.m.
Created at: March 20, 2026, 1:44 p.m.