Triple
T14333871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potsdam-Mittelmark |
E355420
|
entity |
| Predicate | administrativeSeat |
P21613
|
FINISHED |
| Object | Bad Belzig |
E1094009
|
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 Belzig | Statement: [Potsdam-Mittelmark, administrativeSeat, Bad Belzig]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bad Belzig Context triple: [Potsdam-Mittelmark, administrativeSeat, Bad Belzig]
-
A.
Bad Belzig
chosen
Bad Belzig is a historic spa town in the German state of Brandenburg known for its medieval castle and thermal baths.
-
B.
Bad Rothenfelde
Bad Rothenfelde is a spa town in Lower Saxony, Germany, known for its saline springs and health resort facilities.
-
C.
Bad Oeynhausen
Bad Oeynhausen is a spa town in North Rhine-Westphalia, Germany, renowned for its thermal springs and health resorts.
-
D.
Bad Lauchstädt
Bad Lauchstädt is a historic spa town in the German state of Saxony-Anhalt, known for its classical Kurpark and Goethe-Theater.
-
E.
Bad Düben
Bad Düben is a small spa town in Saxony, Germany, known for its health resorts and location near the Dübener Heide nature park.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8c20d2148190bb534bef338e871d |
completed | April 14, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c3d20688190973e37ca38b4afe0 |
completed | May 8, 2026, 2:36 a.m. |
Created at: April 10, 2026, 1:13 a.m.