Triple
T3688872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Harzburg |
E78294
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Vienenburg |
E312129
|
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: Vienenburg | Statement: [Bad Harzburg, locatedNear, Vienenburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vienenburg Context triple: [Bad Harzburg, locatedNear, Vienenburg]
-
A.
Vienenburg
chosen
Vienenburg is a district of Goslar in Lower Saxony, Germany, known for its historic town center and proximity to the Harz Mountains.
-
B.
Rottweil
Rottweil is a historic town in southwestern Germany known for its medieval architecture and as the namesake of the Rottweiler dog breed.
-
C.
Günzburg
Günzburg is a small Bavarian town in southern Germany, historically notable as the birthplace of Nazi physician Josef Mengele.
-
D.
Mühlhausen
Mühlhausen is a historic town in central Germany, known for its well-preserved medieval architecture and cultural heritage.
-
E.
Blaubeuren
Blaubeuren is a historic town in the Alb-Donau district of Baden-Württemberg, Germany, known for its medieval old town and the karst spring Blautopf.
- 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4c960788190b73ede08658846aa |
completed | March 8, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4db01e118819090438d80898cf73b |
completed | March 14, 2026, 3:50 a.m. |
Created at: March 8, 2026, 3:26 p.m.