Triple
T21988779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Shutdown 1 |
E543030
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Franco–Swiss border |
—
|
NE GENERATED |
How this triple was built (1 step)
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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Franco–Swiss border Context triple: [Long Shutdown 1, location, Franco–Swiss border]
-
A.
France–Switzerland border
chosen
The France–Switzerland border is an international boundary in Western Europe separating France and Switzerland, notable for crossing major transport routes and sites such as the CERN research complex near Geneva.
-
B.
Swiss–German border
The Swiss–German border is an international boundary separating Switzerland and Germany, running through regions such as the Upper Rhine and intersecting major urban areas like Basel.
-
C.
French–Italian border
The French–Italian border is the mountainous international boundary between France and Italy, running largely through the Alps and historically fortified and contested.
-
D.
Italian–Swiss border
The Italian–Swiss border is the international boundary separating Italy and Switzerland, winding through the Alps and around various enclaves and exclaves.
-
E.
Switzerland–Liechtenstein border
The Switzerland–Liechtenstein border is a short, open international boundary in Central Europe that largely follows the Rhine River and forms part of the Schengen Area’s internal frontiers.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (1 batch)
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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 8:05 p.m.