Triple
T2400141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vennbahn railway |
E47746
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-border railway |
C9303
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: cross-border railway Context triple: [Vennbahn railway, instanceOf, cross-border railway]
-
A.
road–rail border crossing
A road–rail border crossing is a designated point at an international boundary where both road and railway transport routes intersect or pass through, enabling the controlled movement of vehicles, trains, goods, and passengers between neighboring countries.
-
B.
cross-border transport link
chosen
A cross-border transport link is an infrastructure connection—such as a road, railway, bridge, tunnel, or ferry route—that enables the movement of people and goods between two or more countries.
-
C.
cross-border terminal
A cross-border terminal is a transportation facility located at or near an international boundary that consolidates, processes, and transfers passengers or freight between different countries’ transport networks while handling customs, immigration, and regulatory controls.
-
D.
cross-border area
A cross-border area is a geographic region that spans across the boundaries of two or more countries, where social, economic, environmental, and political interactions occur and are often managed through cooperative arrangements.
-
E.
international border crossing
An international border crossing is a designated point where people, goods, and vehicles are legally inspected and allowed to pass between two countries.
- F. None of above.
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_69a88a1c450c81909f61abb8b6863885 |
completed | March 4, 2026, 7:38 p.m. |
Created at: March 4, 2026, 7:57 p.m.