Triple
T13110310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Elster |
E310952
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Vogtland |
E78598
|
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: Vogtland | Statement: [Bad Elster, locatedIn, Vogtland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vogtland Context triple: [Bad Elster, locatedIn, Vogtland]
-
A.
Vogtland
chosen
Vogtland is a hilly, historically rich region in central Europe spanning parts of Saxony, Thuringia, Bavaria, and the Czech Republic, known for its musical instrument making and scenic landscapes.
-
B.
Unstrut River region
The Unstrut River region is a historical landscape in central Germany characterized by the Unstrut River and its surrounding valleys, towns, and agricultural areas.
-
C.
Hohenelbe
Hohenelbe is the German name for the Czech town of Vrchlabí, a gateway to the Krkonoše (Giant) Mountains region.
-
D.
Wuhle Valley
Wuhle Valley is a river valley in Berlin, Germany, shaped by and named after the Wuhle River.
-
E.
Neumark region
The Neumark region was a historical borderland of Brandenburg-Prussia in eastern Germany, located east of the Oder River and long contested between German and Polish powers.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9817e4f408190b77c198b4157d77a |
completed | April 10, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7265eba0481908417d2bb905874e5 |
completed | May 3, 2026, 10:41 a.m. |
Created at: April 9, 2026, 9:05 p.m.