Triple
T19480304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Salzungen |
E487362
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Werra River |
—
|
NE NERFINISHED |
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: Werra River | Statement: [Bad Salzungen, locatedOn, Werra River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Werra River Context triple: [Bad Salzungen, locatedOn, Werra River]
-
A.
Werra
chosen
The Werra is a major river in central Germany that forms one of the two headstreams of the Weser.
-
B.
Jagst
The Jagst is a river in Baden-Württemberg, Germany, known as one of the major right-bank tributaries of the Neckar and flowing through a largely rural, scenic landscape.
-
C.
Gera River
The Gera River is a waterway in central Germany that flows through the city of Erfurt in the state of Thuringia.
-
D.
Fulda River
The Fulda River is a major river in central Germany that flows through the state of Hesse and joins the Werra River at Hann. Münden to form the Weser.
-
E.
River Wiese
The River Wiese is a river in southwestern Germany and northwestern Switzerland that flows through the Black Forest region before joining the Rhine near Basel.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6343882a88190b3cfa65e6cac80d3 |
completed | April 20, 2026, 2:12 p.m. |
Created at: April 10, 2026, 1:39 p.m.