Triple

T22689200
Position Surface form Disambiguated ID Type / Status
Subject Mkuze E561002 entity
Predicate hasNearbyRiver P8567 FINISHED
Object Mkuze River
The Mkuze River is a significant watercourse in KwaZulu-Natal, South Africa, flowing eastward through wetlands and game reserves before emptying into the northern reaches of Lake St Lucia.
E1644198 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: Mkuze River | Statement: [Mkuze, hasNearbyRiver, Mkuze 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: Mkuze River
Triple: [Mkuze, hasNearbyRiver, Mkuze River]
Generated description
The Mkuze River is a significant watercourse in KwaZulu-Natal, South Africa, flowing eastward through wetlands and game reserves before emptying into the northern reaches of Lake St Lucia.

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_69e2454d71b48190a1f80af9f82b6fcf completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1789931148190925ce9038c16413b completed April 29, 2026, 3:18 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1004483d8481908d8316266460589b completed May 22, 2026, 7:22 a.m.
NEDg Description generation batch_6a100628bf1c819082c4aae29969b5c6 completed May 22, 2026, 7:30 a.m.
NED2 Entity disambiguation (via description) batch_6a1006d990b48190952b59d5685ea626 completed May 22, 2026, 7:33 a.m.
Created at: April 17, 2026, 3:13 p.m.