Triple
T21271234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabie River |
E524260
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | Komatipoort |
—
|
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: Komatipoort | Statement: [Sabie River, nearbySettlement, Komatipoort]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Komatipoort Context triple: [Sabie River, nearbySettlement, Komatipoort]
-
A.
Komatipoort
chosen
Komatipoort is a small town in northeastern South Africa near the Mozambique border, known as a key rail and road gateway between the two countries and for its proximity to Kruger National Park.
-
B.
Koepoort
Koepoort is a historic Dutch city gate known as one of the traditional entrances to a fortified town in the Netherlands.
-
C.
Santpoort
Santpoort is a village in the Dutch province of North Holland, known for its historic estates, dunes, and proximity to the city of Haarlem.
-
D.
Berkelpoort
Berkelpoort is a historic medieval city gate in Zutphen, the Netherlands, that once formed part of the town’s defensive fortifications along the Berkel river.
-
E.
Noupoort
Noupoort is a small railway and transport town in the Northern Cape province of South Africa.
- 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736534c348190a8d29e8d724dd40a |
completed | April 21, 2026, 8:33 a.m. |
Created at: April 16, 2026, 4:01 p.m.