Triple
T12083140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorpe River |
E287732
|
entity |
| Predicate | tributaryOf |
P415
|
FINISHED |
| Object | Röhr River |
E872835
|
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: Röhr River | Statement: [Sorpe River, tributaryOf, Röhr River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Röhr River Context triple: [Sorpe River, tributaryOf, Röhr River]
-
A.
River Röhr
chosen
The River Röhr is a small river in North Rhine-Westphalia, Germany, that flows through the town of Sundern in the Sauerland region.
-
B.
Wiese River
The Wiese River is a tributary of the Rhine flowing through parts of Germany and Switzerland, including the municipality of Riehen near Basel.
-
C.
Heubach river
The Heubach river is a small watercourse in Baden-Württemberg, Germany, that flows through the town of Meßkirch and its surrounding rural landscape.
-
D.
Schwabach River
The Schwabach River is a small river in Bavaria, Germany, that flows through the town of Schwabach before joining the Rednitz River.
-
E.
Kronach River
The Kronach River is a watercourse in northern Bavaria, Germany, that flows through the Kronach district and contributes to the region’s local river system and landscape.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915124e4c8190b0264c2a09e3c2f3 |
completed | April 10, 2026, 3:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6f5b3ced0819083382a0aceda171a |
completed | May 3, 2026, 7:13 a.m. |
Created at: April 8, 2026, 9:48 p.m.