Triple
T16156414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mittelrhein |
E392054
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Oberwesel |
E351913
|
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: Oberwesel | Statement: [Mittelrhein, hasTown, Oberwesel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oberwesel Context triple: [Mittelrhein, hasTown, Oberwesel]
-
A.
Oberwesel
chosen
Oberwesel is a historic town on the Middle Rhine in Germany, renowned for its well-preserved medieval walls, castles, and picturesque riverside setting.
-
B.
Wörth am Rhein
Wörth am Rhein is a town in the German state of Rhineland-Palatinate, situated on the Rhine River near Karlsruhe and known for its industrial facilities and transport links.
-
C.
Merzig
Merzig is a town in the Saarland region of western Germany, near the borders with France and Luxembourg.
-
D.
Kusel
Kusel is a small town in the German state of Rhineland-Palatinate, known as the administrative center of the Kusel district in the Western Palatinate region.
-
E.
Elchingen
Elchingen is a municipality in southern Germany, historically notable as the site of a major Napoleonic victory during the War of the Third Coalition.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21e5aa57c8190a9d89dd57e30318f |
completed | April 17, 2026, 11:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff7ae46dc81908cba9152a6080c3a |
completed | May 10, 2026, 3:12 a.m. |
Created at: April 10, 2026, 5:01 a.m.