Triple

T34374621
Position Surface form Disambiguated ID Type / Status
Subject Belfast, Mpumalanga E882252 entity
Predicate region P40 FINISHED
Object Nkangala District
Nkangala District is an administrative district in South Africa’s Mpumalanga province, known for its coal mining, power generation, and industrial activities.
E2210041 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: Nkangala District | Statement: [Belfast, Mpumalanga, region, Nkangala District]
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: Nkangala District
Triple: [Belfast, Mpumalanga, region, Nkangala District]
Generated description
Nkangala District is an administrative district in South Africa’s Mpumalanga province, known for its coal mining, power generation, and industrial activities.

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_69f349bf5d7481908dd5da4cbdf74047 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71853d9348190a0346e0dea633174 completed May 3, 2026, 9:41 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3e8c1390c4819084f740a29c6a156c completed June 26, 2026, 2:26 p.m.
NEDg Description generation batch_6a3e94bce86c8190b025e79699e31e7e completed June 26, 2026, 3:03 p.m.
NED2 Entity disambiguation (via description) batch_6a3e9e99bdf081909934fab6490220d7 completed June 26, 2026, 3:45 p.m.
Created at: May 1, 2026, 1:59 a.m.