Triple

T23528332
Position Surface form Disambiguated ID Type / Status
Subject Mamprusi E576493 entity
Predicate relatedEthnicGroups P1969 FINISHED
Object Nanumba 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: Nanumba | Statement: [Mamprusi, relatedEthnicGroups, Nanumba]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nanumba
Context triple: [Mamprusi, relatedEthnicGroups, Nanumba]
  • A. Nanumba chosen
    The Nanumba are an ethnic group in northern Ghana known for their distinct language, chieftaincy traditions, and agrarian lifestyle.
  • B. Nkerefi
    Nkerefi is a rural community located in Nkanu East Local Government Area of Enugu State in southeastern Nigeria.
  • C. Lugbara
    Lugbara is a Central Sudanic language spoken primarily by the Lugbara people in northwestern Uganda and parts of the Democratic Republic of the Congo and South Sudan.
  • D. Kangulumira
    Kangulumira is a small town in central Uganda located within Kayunga District.
  • E. Musumba
    Musumba is the historic royal capital of the Lunda Kingdom, serving as a central political and cultural seat for the Lunda people in Central Africa.
  • 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_69e245f5a8848190a2ba42e271c6c31f completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1ac758038819098f5f597be39274e completed April 29, 2026, 7 a.m.
Created at: April 17, 2026, 6:09 p.m.