Triple
T15538799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vogtlandkreis |
E370419
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bad Elster |
E310952
|
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 Elster | Statement: [Vogtlandkreis, contains, Bad Elster]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bad Elster Context triple: [Vogtlandkreis, contains, Bad Elster]
-
A.
Bad Elster
chosen
Bad Elster is a historic spa town in Saxony, Germany, renowned for its mineral springs and role as a traditional health resort.
-
B.
Bad Rothenfelde
Bad Rothenfelde is a spa town in Lower Saxony, Germany, known for its saline springs and health resort facilities.
-
C.
Bad Eilsen
Bad Eilsen is a spa town in Lower Saxony, Germany, historically notable for serving as the post–World War II headquarters of the Royal Air Force’s British Air Forces of Occupation.
-
D.
Bad Heilbrunn
Bad Heilbrunn is a spa municipality in Upper Bavaria, Germany, known for its health resorts and scenic Alpine foothills setting.
-
E.
Bad Belzig
Bad Belzig is a historic spa town in the German state of Brandenburg known for its medieval castle and thermal baths.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04430b5188190a555a3cd4fb0c61c |
completed | April 16, 2026, 2:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff3d626e688190bd93481cfd6cb255 |
completed | May 9, 2026, 1:57 p.m. |
Created at: April 10, 2026, 4:07 a.m.