Triple
T12917285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Tölz-Wolfratshausen |
E309018
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Bad Tölz |
E10394
|
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 Tölz | Statement: [Bad Tölz-Wolfratshausen, namedAfter, Bad Tölz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bad Tölz Context triple: [Bad Tölz-Wolfratshausen, namedAfter, Bad Tölz]
-
A.
Bad Tölz
chosen
Bad Tölz is a Bavarian spa town in southern Germany known for its historic old town, alpine scenery, and traditional German architecture.
-
B.
Bad Mergentheim
Bad Mergentheim is a historic spa town in the German state of Baden-Württemberg, renowned for its mineral springs and picturesque setting in the Tauber Valley.
-
C.
Bad Tölz-Wolfratshausen
Bad Tölz-Wolfratshausen is a rural district in Upper Bavaria, Germany, known for its picturesque Alpine foothills, spa towns, and traditional Bavarian culture.
-
D.
Bad Rothenfelde
Bad Rothenfelde is a spa town in Lower Saxony, Germany, known for its saline springs and health resort facilities.
-
E.
Bad Salzungen
Bad Salzungen is a spa town in Thuringia, Germany, known for its saline springs 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971a1e8088190af697629baecf59f |
completed | April 10, 2026, 9:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8d101e08190b31d6aaaecf96507 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 5:41 p.m.