Triple
T1117546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basel–Mulhouse railway |
E11134
|
entity |
| Predicate | borderCrossing |
P4105
|
FINISHED |
| Object | Swiss–French border near Basel |
—
|
LITERAL 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: Swiss–French border near Basel | Statement: [Basel–Mulhouse railway, borderCrossing, Swiss–French border near Basel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCrossing Context triple: [Basel–Mulhouse railway, borderCrossing, Swiss–French border near Basel]
-
A.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
B.
hasBorderCrossing
chosen
Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
-
C.
borderEstablished
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
-
D.
hasBorderCrossingFunction
Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
-
E.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
- F. None of above.
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_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4562f48190831e959f5f309956 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.