Triple
T19515898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyeongui Line rail connection |
E488276
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-border railway link |
C20620
|
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 link Context triple: [Gyeongui Line rail connection, instanceOf, cross-border railway link]
-
A.
cross-border transport link
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.
-
B.
international railway
chosen
An international railway is a rail transport system or route that connects and facilitates the movement of passengers and freight between two or more countries across their national borders.
-
C.
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.
-
D.
joint railway
A joint railway is a rail line or network that is owned, operated, or managed collaboratively by two or more railway companies or authorities, sharing infrastructure, services, and responsibilities.
-
E.
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.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:40 p.m.