Triple

T31944466
Position Surface form Disambiguated ID Type / Status
Subject Tsomo, Eastern Cape, South Africa E815612 entity
Predicate locatedOnRiver P165 FINISHED
Object Tsomo River
Tsomo River is a watercourse in South Africa’s Eastern Cape province that flows through rural landscapes and supports local communities and agriculture.
E2077130 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: Tsomo River | Statement: [Tsomo, Eastern Cape, South Africa, locatedOnRiver, Tsomo River]
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: Tsomo River
Triple: [Tsomo, Eastern Cape, South Africa, locatedOnRiver, Tsomo River]
Generated description
Tsomo River is a watercourse in South Africa’s Eastern Cape province that flows through rural landscapes and supports local communities and agriculture.

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_69f348f42d188190a33fc8d20ec50517 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b2782830819097212dbb2c9cc496 completed May 3, 2026, 2:27 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3692b65d1c8190b6940e41c91cdd06 completed June 20, 2026, 1:16 p.m.
NEDg Description generation batch_6a3693978aa881909be8384c3d62bc33 completed June 20, 2026, 1:20 p.m.
NED2 Entity disambiguation (via description) batch_6a3694bc096081909982b082aec3241d completed June 20, 2026, 1:25 p.m.
Created at: May 1, 2026, 12:06 a.m.