Triple
T3114417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rednitz River |
E65025
|
entity |
| Predicate | hasGermanName |
P1435
|
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: [Rednitz River, hasGermanName, Rednitz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rednitz Context triple: [Rednitz River, hasGermanName, 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.
Nischel
Nischel is the local colloquial nickname for the large Karl Marx Monument in Chemnitz, Germany.
-
C.
Dietl
Dietl is a German surname most notably associated with Eduard Dietl, a World War II German general.
-
D.
Baumwerder
Baumwerder is a small island located in Tegeler See, a lake in the Berlin district of Reinickendorf, Germany.
-
E.
Zwenkau
Zwenkau is a small town in the Free State of Saxony in eastern Germany, situated near Leipzig and known for its proximity to former lignite mining areas now being transformed into lake landscapes.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada43dca688190ab041554220c5271 |
completed | March 8, 2026, 4:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b2039b11d4819095ee77d84d6e7b8a |
completed | March 12, 2026, 12:06 a.m. |
Created at: March 8, 2026, 3:04 p.m.