Triple
T3964394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeastern Zimbabwe |
E85979
|
entity |
| Predicate | hasRiver |
P165
|
FINISHED |
| Object |
Runde River
Runde River is a major river in southeastern Zimbabwe that flows through the Lowveld region and into the Save River system.
|
E618528
|
NE FINISHED |
How this triple was built (4 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: Runde River | Statement: [Southeastern Zimbabwe, hasRiver, Runde River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runde River Context triple: [Southeastern Zimbabwe, hasRiver, Runde River]
-
A.
Tecka River
The Tecka River is a Patagonian watercourse in Argentina that feeds into the larger Chubut River system.
-
B.
Siang River
The Siang River is a major river in northeastern India that forms the upper course of the Brahmaputra as it flows from Tibet into Arunachal Pradesh.
-
C.
Nyari River
The Nyari River is a regional river in the Indian state of Gujarat that flows through and helps sustain the city of Rajkot.
-
D.
Osyotr River
The Osyotr River is a river in western Russia that flows through the Moscow and Tula regions before joining the Oka River.
-
E.
Yeso River
The Yeso River is a significant Andean watercourse in central Chile that feeds into the Maipo River and helps supply water to the Santiago metropolitan region.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Runde River Triple: [Southeastern Zimbabwe, hasRiver, Runde River]
Generated description
Runde River is a major river in southeastern Zimbabwe that flows through the Lowveld region and into the Save River system.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Runde River Target entity description: Runde River is a major river in southeastern Zimbabwe that flows through the Lowveld region and into the Save River system.
-
A.
Tecka River
The Tecka River is a Patagonian watercourse in Argentina that feeds into the larger Chubut River system.
-
B.
Siang River
The Siang River is a major river in northeastern India that forms the upper course of the Brahmaputra as it flows from Tibet into Arunachal Pradesh.
-
C.
Nyari River
The Nyari River is a regional river in the Indian state of Gujarat that flows through and helps sustain the city of Rajkot.
-
D.
Osyotr River
The Osyotr River is a river in western Russia that flows through the Moscow and Tula regions before joining the Oka River.
-
E.
Yeso River
The Yeso River is a significant Andean watercourse in central Chile that feeds into the Maipo River and helps supply water to the Santiago metropolitan region.
- F. None of above. chosen
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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef97326888190bbfe15b218e3112e |
completed | March 9, 2026, 4:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c712687f408190ac948dcc990e8e08 |
completed | March 27, 2026, 11:27 p.m. |
| NEDg | Description generation | batch_69c7132017a881909a8f4a8d4635d53f |
completed | March 27, 2026, 11:30 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69c715cc0c9c8190aae641eaffa5bd7b |
completed | March 27, 2026, 11:42 p.m. |
Created at: March 9, 2026, 3:31 p.m.