Triple
T9814803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingelheim am Rhein |
E238373
|
entity |
| Predicate | twinTown |
P1072
|
FINISHED |
| Object | Nieder-Olm |
E273636
|
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: Nieder-Olm | Statement: [Ingelheim am Rhein, twinTown, Nieder-Olm]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nieder-Olm Context triple: [Ingelheim am Rhein, twinTown, Nieder-Olm]
-
A.
Nieder-Olm
chosen
Nieder-Olm is a small town in the Mainz-Bingen district of Rhineland-Palatinate, western Germany, known for its winegrowing and proximity to the city of Mainz.
-
B.
Oberstedten
Oberstedten is a district of the town Oberursel in Hesse, Germany, situated near the Taunus mountain range.
-
C.
Oberselters
Oberselters is a district of the spa town Bad Camberg in Hesse, Germany, known for its rural character within the Taunus region.
-
D.
Ötlingen
Ötlingen is a village-like district of the town of Weil am Rhein in the southwestern German state of Baden-Württemberg, near the borders with France and Switzerland.
-
E.
Schambach
Schambach is a small river in Bavaria, Germany, that flows into the Altmühl as one of its tributaries.
- 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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb2f19660819083e3f15780352052 |
completed | April 2, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1cc67db68819093217c9a74e72fbf |
completed | April 5, 2026, 2:43 a.m. |
Created at: March 30, 2026, 8:30 p.m.