Triple

T21824862
Position Surface form Disambiguated ID Type / Status
Subject San languages E538822 entity
Predicate hasExampleLanguage P7390 FINISHED
Object Khwe 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: Khwe | Statement: [San languages, hasExampleLanguage, Khwe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khwe
Context triple: [San languages, hasExampleLanguage, Khwe]
  • A. Khwe chosen
    The Khwe are an indigenous San people of southern Africa, traditionally semi-nomadic hunter-gatherers living mainly in the Okavango and Caprivi regions of Botswana and Namibia.
  • B. Nkoya
    Nkoya is a Bantu language spoken primarily in western Zambia by the Nkoya people.
  • C. Inibaloi
    Inibaloi is an Austronesian language spoken by the Ibaloi people of the northern Philippines, particularly in Benguet province on Luzon.
  • D. Kamba
    Kamba is a Bantu language spoken primarily by the Akamba people of Kenya, known for its rich oral traditions and regional cultural significance.
  • E. Ndau
    Ndau is a Southern Bantu language spoken primarily in central Mozambique and eastern Zimbabwe, closely related to Shona.
  • 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_69e0c475038c8190abb9b1a20eb8ff50 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f091307d408190a92b65c3f39682a8 completed April 28, 2026, 10:51 a.m.
Created at: April 16, 2026, 6:54 p.m.