Triple
T907860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rednitz |
E19589
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object | Schwabach (river) |
E110122
|
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: Schwabach (river) | Statement: [Rednitz, hasTributary, Schwabach (river)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schwabach (river) Context triple: [Rednitz, hasTributary, Schwabach (river)]
-
A.
Schwabach
chosen
Schwabach is a historic town in northern Bavaria, Germany, known for its traditional gold-beating craft and well-preserved old town.
-
B.
Chemnitz River
The Chemnitz River is a waterway in the German state of Saxony that flows through and gives its name to the city of Chemnitz.
-
C.
Würschnitz
Würschnitz is a small river in Saxony, Germany, that serves as one of the tributaries feeding into the Chemnitz River.
-
D.
Pegnitz River
The Pegnitz River is a river in the German state of Bavaria that flows through the city of Nuremberg and joins the Rednitz to form the Regnitz.
-
E.
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.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2cdc1788190a704809404f49986 |
completed | March 1, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a9339e557c81908d4d44f922994ba0 |
completed | March 5, 2026, 7:41 a.m. |
Created at: March 1, 2026, 7:39 p.m.