Triple

T38530712
Position Surface form Disambiguated ID Type / Status
Subject Madibeng Local Municipality E923354 entity
Predicate contains P35 FINISHED
Object Skeerpoort
Skeerpoort is a rural village in South Africa’s North West province, known for its farming community and scenic setting near the Magaliesberg mountains.
E2274633 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: Skeerpoort | Statement: [Madibeng Local Municipality, contains, Skeerpoort]
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: Skeerpoort
Triple: [Madibeng Local Municipality, contains, Skeerpoort]
Generated description
Skeerpoort is a rural village in South Africa’s North West province, known for its farming community and scenic setting near the Magaliesberg mountains.

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_69f76ea8f6348190a5c03fb6292bbee3 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcd2b8f2d081908a44bbadbdc2240a completed May 7, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_6a41e028ec4c8190b1b2db306f447fc5 completed June 29, 2026, 3:02 a.m.
NEDg Description generation batch_6a41e144b5288190a0151e596e7ceef6 completed June 29, 2026, 3:06 a.m.
NED2 Entity disambiguation (via description) batch_6a41e1c14b4c81908b2d6358dbd3ae0f completed June 29, 2026, 3:08 a.m.
Created at: May 3, 2026, 4:32 p.m.