Triple
T13754658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donau-Ries |
E330443
|
entity |
| Predicate | traversedByRiver |
P165
|
FINISHED |
| Object | Wörnitz |
E567873
|
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: Wörnitz | Statement: [Donau-Ries, traversedByRiver, Wörnitz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wörnitz Context triple: [Donau-Ries, traversedByRiver, Wörnitz]
-
A.
Würschnitz
Würschnitz is a small river in Saxony, Germany, that serves as one of the tributaries feeding into the Chemnitz River.
-
B.
Weschnitz
Weschnitz is a river in southwestern Germany that flows from the Odenwald hills through Hesse and Baden-Württemberg before joining the Rhine.
-
C.
River Wörnitz
chosen
River Wörnitz is a river in Bavaria, Germany, that flows through historic towns such as Dinkelsbühl before joining the Danube.
-
D.
Pließnitz
Pließnitz is a small river in eastern Germany that flows through Saxony and joins the Lusatian Neisse.
-
E.
Wakenitz
Wakenitz is a river in northern Germany that flows through the city of Lübeck and connects the Ratzeburger See to the Trave 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02179c948190a652cc8c586e418f |
completed | April 14, 2026, 9 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c0ded1e0819097ef42533357caf8 |
completed | May 3, 2026, 9:40 p.m. |
Created at: April 9, 2026, 10:09 p.m.