Triple

T38493221
Position Surface form Disambiguated ID Type / Status
Subject Nkomo E918111 entity
Predicate hasNotableBearer P458 FINISHED
Object Emmerson Nkomo
Emmerson Nkomo is an individual notable enough to be recognized as a prominent bearer of the surname Nkomo.
E2283337 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: Emmerson Nkomo | Statement: [Nkomo, hasNotableBearer, Emmerson Nkomo]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Emmerson Nkomo
Triple: [Nkomo, hasNotableBearer, Emmerson Nkomo]
Generated description
Emmerson Nkomo is an individual notable enough to be recognized as a prominent bearer of the surname Nkomo.

Provenance (5 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_69f76e9894208190a129a553a60ca58c completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fcd243878081909bf47996f9428045 completed May 7, 2026, 5:56 p.m.
NED1 Entity disambiguation (via context triple) batch_6a424a03ce2881909a2fa0210583e01c completed June 29, 2026, 10:33 a.m.
NEDg Description generation batch_6a424a8948608190b4607a67466c8372 completed June 29, 2026, 10:35 a.m.
NED2 Entity disambiguation (via description) batch_6a424b5e8e9c8190818d0ef2f3f43398 completed June 29, 2026, 10:39 a.m.
Created at: May 3, 2026, 4:31 p.m.