Triple
T19515900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyeongui Line rail connection |
E488276
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inter-Korean transport infrastructure |
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: inter-Korean transport infrastructure Context triple: [Gyeongui Line rail connection, instanceOf, inter-Korean transport infrastructure]
-
A.
transport infrastructure agreement
A transport infrastructure agreement is a formal contract between parties that defines the responsibilities, funding, timelines, and performance standards for planning, building, operating, or maintaining transportation facilities such as roads, railways, ports, or airports.
-
B.
Busan Metro station
A Busan Metro station is a designated facility along the Busan subway network where trains stop to allow passengers to board, alight, and transfer between lines or other modes of transportation.
-
C.
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.
-
D.
combined road and rail bridge–tunnel
A combined road and rail bridge–tunnel is a hybrid transportation structure that integrates both bridge and tunnel segments to carry vehicular and rail traffic across or under a geographic obstacle such as a body of water or valley.
-
E.
dong of South Korea
A dong of South Korea is the smallest administrative neighborhood unit within a city or district, responsible for local governance and community services.
- 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.