Triple
T15503302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulhouse tramway |
E379014
|
entity |
| Predicate | connectsDistrict |
P2564
|
FINISHED |
| Object | Riedisheim |
E1174697
|
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: Riedisheim | Statement: [Mulhouse tramway, connectsDistrict, Riedisheim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Riedisheim Context triple: [Mulhouse tramway, connectsDistrict, Riedisheim]
-
A.
Riedisheim
chosen
Riedisheim is a commune in northeastern France’s Grand Est region, situated near the city of Mulhouse in the Haut-Rhin department.
-
B.
Rheingönheim
Rheingönheim is a district of the industrial city of Ludwigshafen am Rhein in the German state of Rhineland-Palatinate.
-
C.
Diedelsheim
Diedelsheim is a district of the town of Bretten in the state of Baden-Württemberg in southwestern Germany.
-
D.
Ottmarsheim
Ottmarsheim is a commune in northeastern France’s Alsace region, known for its historic Romanesque church and location along the Rhine.
-
E.
Geispolsheim
Geispolsheim is a commune in northeastern France’s Grand Est region, situated near Strasbourg and known for its mix of traditional Alsatian character and modern industrial and commercial zones.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fcc5bb88190b8a9a81419a9a38b |
completed | April 16, 2026, 1:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb593258081909dcaf2b37fd28e63 |
completed | May 9, 2026, 10:30 p.m. |
Created at: April 10, 2026, 3:54 a.m.