Triple
T16823833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potchefstroom |
E408963
|
entity |
| Predicate | river |
P165
|
FINISHED |
| Object | Mooirivier |
—
|
NE NERFINISHED |
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: Mooirivier | Statement: [Potchefstroom, river, Mooirivier]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mooirivier Context triple: [Potchefstroom, river, Mooirivier]
-
A.
Mooi River
chosen
Mooi River is a small town in KwaZulu-Natal, South Africa, known for its agricultural surroundings and role as a stopover point along major transport routes.
-
B.
Dri River
The Dri River is a tributary watercourse in the northeastern Indian state of Arunachal Pradesh, contributing to the Dibang River system within the Brahmaputra basin.
-
C.
Riet River
The Riet River is a watercourse in South Africa that played a notable role as a strategic crossing point during the Second Boer War.
-
D.
Grobbelaars River
Grobbelaars River is a watercourse in South Africa’s Western Cape that flows through the town of Oudtshoorn in the semi-arid Little Karoo region.
-
E.
Touws River
Touws River is a small town in South Africa’s Western Cape, known historically as a railway junction and gateway to the semi-arid Karoo region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e838e881908b650194c9b94886 |
completed | April 18, 2026, 4:35 p.m. |
Created at: April 10, 2026, 5:23 a.m.