Triple
T8020364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unstrut River region |
E186724
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bad Langensalza |
E670174
|
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: Bad Langensalza | Statement: [Unstrut River region, contains, Bad Langensalza]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bad Langensalza Context triple: [Unstrut River region, contains, Bad Langensalza]
-
A.
Bad Langensalza
chosen
Bad Langensalza is a historic spa town in Thuringia, Germany, known for its thermal baths, well-preserved old town, and numerous themed gardens.
-
B.
Bad Klosterlausnitz
Bad Klosterlausnitz is a spa town in the German state of Thuringia, known for its therapeutic facilities and surrounding forested landscapes.
-
C.
Bad Salzungen
Bad Salzungen is a spa town in Thuringia, Germany, known for its saline springs and therapeutic health resorts.
-
D.
Treuenbrietzen
Treuenbrietzen is a historic town in the German state of Brandenburg, known for its medieval architecture and role in Reformation-era history.
-
E.
Lülsfeld
Lülsfeld is a small municipality in the Schweinfurt district of Lower Franconia in northern Bavaria, Germany.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8d90488190b57d1e748e272061 |
completed | March 31, 2026, 3:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc56c82824819082e93eddc40bfad1 |
completed | March 31, 2026, 11:20 p.m. |
Created at: March 30, 2026, 5:20 p.m.