Triple
T2025131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fürth |
E44190
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Rednitz River |
E65025
|
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: Rednitz River | Statement: [Fürth, locatedOn, Rednitz River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rednitz River Context triple: [Fürth, locatedOn, Rednitz River]
-
A.
Rednitz River
chosen
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.
Blau River
The Blau River is a small river in the state of Baden-Württemberg in southern Germany, known for flowing through the Swabian Jura and joining the Danube at Ulm.
-
C.
Linde River
The Linde River is a lesser-known watercourse in Russia that feeds into the major Siberian Lena River system.
-
D.
Dore River
The Dore River is a river in central France that flows through the Massif Central and joins the Allier River, contributing to the Loire basin.
-
E.
Limmat River
The Limmat River is a major Swiss waterway that flows out of Lake Zurich and runs through the city of Zurich before joining the Aare River.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f3faa08190a48ae1355d6e009f |
completed | March 7, 2026, 5:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af1f702640819085b5d5d69615b92a |
completed | March 9, 2026, 7:28 p.m. |
Created at: March 4, 2026, 7:38 p.m.