Triple
T8663496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landkreis Reutlingen |
E205604
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bad Urach |
E727135
|
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 Urach | Statement: [Landkreis Reutlingen, contains, Bad Urach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bad Urach Context triple: [Landkreis Reutlingen, contains, Bad Urach]
-
A.
Bad Urach
chosen
Bad Urach is a historic spa town in the Swabian Alb region of Baden-Württemberg, Germany, known for its thermal baths, medieval architecture, and nearby waterfalls.
-
B.
Bad Iburg
Bad Iburg is a small spa town in Lower Saxony, Germany, known for its historic Iburg Castle and surrounding Teutoburg Forest scenery.
-
C.
Bad Nauheim
Bad Nauheim is a spa town in the German state of Hesse, historically known for its therapeutic mineral springs and health resorts.
-
D.
Bad Brambach
Bad Brambach is a German spa town in the Vogtland region of Saxony, renowned for its mineral springs and therapeutic health resorts.
-
E.
Bad Tennstedt
Bad Tennstedt is a small spa town in Thuringia, Germany, known for its mineral springs and location in the Unstrut river landscape.
- 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc489f7edc8190bde1b4dc09249207 |
completed | March 31, 2026, 10:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cecd0d95ec81908669ee35f0987be7 |
completed | April 2, 2026, 8:09 p.m. |
Created at: March 30, 2026, 6:30 p.m.