Triple
T21391604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilge River |
E527665
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Klein Wilge River |
—
|
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: Klein Wilge River | Statement: [Wilge River, hasTributary, Klein Wilge River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Klein Wilge River Context triple: [Wilge River, hasTributary, Klein Wilge River]
-
A.
Rednitz River
The Rednitz River is a river in Franconia, Germany, that flows through cities such as Fürth before joining the Pegnitz to form the Regnitz.
-
B.
Ziese River
The Ziese River is a small river in northeastern Germany that drains into the Szczecin Lagoon along the Baltic Sea coast.
-
C.
Fuhse River
The Fuhse River is a tributary waterway in northern Germany that flows through Lower Saxony before joining the Aller River.
-
D.
Wilge River
chosen
The Wilge River is a significant river in South Africa that flows through the Free State and Mpumalanga provinces before joining the Vaal River.
-
E.
Wurm River
The Wurm River is a small river in western Germany that flows through the city of Aachen before joining the Rur.
- 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b113690c81909c0a378fddba5d3a |
completed | April 22, 2026, 11:29 a.m. |
Created at: April 16, 2026, 5:13 p.m.