Triple
T7407310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludwigshafen am Rhein |
E170906
|
entity |
| Predicate | hasDistrict |
P459
|
FINISHED |
| Object | Oggersheim |
E66380
|
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: Oggersheim | Statement: [Ludwigshafen am Rhein, hasDistrict, Oggersheim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oggersheim Context triple: [Ludwigshafen am Rhein, hasDistrict, Oggersheim]
-
A.
Oggersheim
chosen
Oggersheim is a district of Ludwigshafen am Rhein in Germany, best known as the longtime home of former Chancellor Helmut Kohl.
-
B.
Igersheim
Igersheim is a small municipality in the Main-Tauber district of Baden-Württemberg in southern Germany.
-
C.
Obergoms
Obergoms is a municipality in the canton of Valais in southwestern Switzerland, known for its high Alpine landscapes and traditional mountain villages.
-
D.
Freiolsheim
Freiolsheim is a village and district of the town of Gaggenau in the Rastatt district of Baden-Württemberg, Germany.
-
E.
Orisbach
Orisbach is a small stream in Switzerland that serves as a tributary of the Ergolz River in the canton of Basel-Landschaft.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f298f2388190afc944c9bc78749a |
completed | March 27, 2026, 9:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c84ee52fd48190adebb6ae555663a4 |
completed | March 28, 2026, 9:57 p.m. |
Created at: March 27, 2026, 3:10 p.m.