Triple
T1117524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basel–Mulhouse railway |
E11134
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Mulhouse |
E78039
|
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: Mulhouse | Statement: [Basel–Mulhouse railway, connects, Mulhouse]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mulhouse Context triple: [Basel–Mulhouse railway, connects, Mulhouse]
-
A.
Mulhouse
chosen
Mulhouse is an industrial city in northeastern France near the Swiss and German borders, known for its textile heritage and major technical museums.
-
B.
Strasbourg
Strasbourg is a major French city on the Rhine known for hosting key European institutions, including the European Parliament and the Council of Europe.
-
C.
Illkirch-Graffenstaden
Illkirch-Graffenstaden is a suburban commune in northeastern France, located just south of Strasbourg in the Grand Est region.
-
D.
Besançon
Besançon is a historic city in eastern France, known for its well-preserved Vauban fortifications, rich cultural heritage, and role as a regional administrative and educational center.
-
E.
Lancy
Lancy is a suburban municipality in western Switzerland that forms part of the urban area of Geneva.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bba425a8819099116e479552332e |
completed | March 1, 2026, 10:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adbf33c7808190962fb6c2496b4ec7 |
completed | March 8, 2026, 6:25 p.m. |
Created at: March 1, 2026, 7:43 p.m.