Triple

T11793177
Position Surface form Disambiguated ID Type / Status
Subject Thabo Makgoba E280437 entity
Predicate familyName P18 FINISHED
Object Makgoba E280437 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: Makgoba | Statement: [Thabo Makgoba, familyName, Makgoba]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Makgoba
Context triple: [Thabo Makgoba, familyName, Makgoba]
  • A. Makgoba chosen
    Makgoba is a South African surname most prominently associated with Thabo Makgoba, the Anglican Archbishop of Cape Town.
  • B. Mokorotlo
    Mokorotlo is a traditional Basotho conical hat, typically woven from grass, that serves as a national cultural symbol of Lesotho.
  • C. Mabalako
    Mabalako is a health zone in North Kivu Province in the eastern Democratic Republic of the Congo, known for being heavily affected by Ebola outbreaks.
  • D. Thokoza
    Thokoza is a township in the East Rand region of Gauteng, South Africa, historically known for its role in anti-apartheid struggles and community activism.
  • E. Makhuwa
    Makhuwa is a major Bantu language spoken primarily in northern Mozambique by the Makhuwa people.
  • 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_69d6ab258b808190b1735835c841e3a4 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a5a082d08190a42541396a06ed98 completed April 10, 2026, 7:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69f130fd7b9881909e79ecb49fe98d30 completed April 28, 2026, 10:13 p.m.
Created at: April 8, 2026, 9:42 p.m.