Triple
T13674197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | district of Roth |
E327828
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Rednitz |
E19589
|
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 | Statement: [district of Roth, locatedOnRiver, Rednitz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rednitz Context triple: [district of Roth, locatedOnRiver, Rednitz]
-
A.
Rednitz
chosen
The Rednitz is a river in Bavaria, Germany, that flows through cities such as Fürth and joins with the Pegnitz to form the Regnitz.
-
B.
Duttweiler
Duttweiler is a village and local district (Ortsteil) of Neustadt an der Weinstraße in the Rhineland-Palatinate wine-growing region of Germany.
-
C.
Bramsche
Bramsche is a town in Lower Saxony, Germany, known for its location near Osnabrück and its historical textile industry.
-
D.
Schlenze
Schlenze is a small river in central Germany, known as a tributary of the Saale flowing through the state of Saxony-Anhalt.
-
E.
Schwanebeck
Schwanebeck is a former municipality in Brandenburg, Germany, that now forms part of the town of Panketal.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc65aab348190a6611f5765f8392d |
completed | April 12, 2026, 4:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78b145fa081908521c103201f3afe |
completed | May 3, 2026, 5:51 p.m. |
Created at: April 9, 2026, 9:53 p.m.