Triple

T13611248
Position Surface form Disambiguated ID Type / Status
Subject Ivory Park E325191 entity
Predicate hasLanguage P15 FINISHED
Object Southern Ndebele E26699 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: Southern Ndebele | Statement: [Ivory Park, hasLanguage, Southern Ndebele]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Southern Ndebele
Context triple: [Ivory Park, hasLanguage, Southern Ndebele]
  • A. Southern Ndebele chosen
    Southern Ndebele is a Bantu language spoken primarily in South Africa, known for its distinctive click sounds and cultural association with the Ndebele people.
  • B. Northern Ndebele
    Northern Ndebele is a Bantu language of the Nguni group spoken primarily in southwestern Zimbabwe and closely related to Zulu.
  • C. Southwest Bantu
    Southwest Bantu is a subgroup of the Bantu language family comprising closely related languages spoken primarily in southwestern Africa.
  • D. Northwest Bantu
    Northwest Bantu is a subgroup of Bantu languages spoken in parts of Central and West-Central Africa, encompassing languages such as Fang.
  • E. Southern Swati
    Southern Swati is a regional dialect of the siSwati language spoken primarily in the southern parts of Eswatini and neighboring areas.
  • 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_69d8076aae28819092cf636190ee5529 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb0aa9a1481908c6f92495aff86c6 completed April 12, 2026, 2:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69f77f9a9f9c81909b0a8f4f51c461ae completed May 3, 2026, 5:02 p.m.
Created at: April 9, 2026, 9:50 p.m.