Triple
T10289555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Hersfeld |
E241324
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Bad Salzungen |
E487362
|
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 Salzungen | Statement: [Bad Hersfeld, hasTwinTown, Bad Salzungen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bad Salzungen Context triple: [Bad Hersfeld, hasTwinTown, Bad Salzungen]
-
A.
Bad Salzungen
chosen
Bad Salzungen is a spa town in Thuringia, Germany, known for its saline springs and therapeutic health resorts.
-
B.
Bad Salzuflen
Bad Salzuflen is a German spa town in the Lippe district of North Rhine-Westphalia, known for its saltwater springs and historic half-timbered architecture.
-
C.
Bad Schönau
Bad Schönau is a small spa town in Lower Austria known for its therapeutic mineral springs and tranquil rural setting.
-
D.
Bad Schussenried
Bad Schussenried is a spa town in southern Germany known for its historic monastery complex and scenic location in Upper Swabia.
-
E.
Bad Salzdetfurth
Bad Salzdetfurth is a spa town in Lower Saxony, Germany, known for its historic saltworks and therapeutic health resorts.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2d192288190a64c27a4f26b71fc |
completed | April 7, 2026, 9:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6f8556f4081908390bc5c14dcf560 |
completed | April 9, 2026, 12:52 a.m. |
Created at: April 6, 2026, 11:41 a.m.