Triple
T13950017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Dizier |
E335494
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Germersheim |
E722426
|
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: Germersheim | Statement: [Saint-Dizier, hasTwinTown, Germersheim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Germersheim Context triple: [Saint-Dizier, hasTwinTown, Germersheim]
-
A.
Germersheim
chosen
Germersheim is a town in the Rhineland-Palatinate region of southwestern Germany, situated on the Rhine River and known for its historic fortress and role as a local administrative and transport hub.
-
B.
Rheingönheim
Rheingönheim is a district of the industrial city of Ludwigshafen am Rhein in the German state of Rhineland-Palatinate.
-
C.
Griesheim
Griesheim is a town in the German state of Hesse, located near the city of Darmstadt and known for its residential character and local industry.
-
D.
Igersheim
Igersheim is a small municipality in the Main-Tauber district of Baden-Württemberg in southern Germany.
-
E.
Meckesheim
Meckesheim is a small municipality in southwestern Germany’s Rhine-Neckar region, known as a rural community with historical roots in Baden-Württemberg.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e131c608190b4ffdbada24a3208 |
completed | April 14, 2026, 12:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbac89ebd48190ab448f74daf82a96 |
completed | May 6, 2026, 9:03 p.m. |
Created at: April 9, 2026, 10:17 p.m.