Triple
T30513119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyeongbu Line (local services) |
E776483
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rail transport service in South Korea |
C75
|
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: rail transport service in South Korea Context triple: [Gyeongbu Line (local services), instanceOf, rail transport service in South Korea]
-
A.
Seoul Metropolitan Subway station
A Seoul Metropolitan Subway station is a designated transit facility within the Seoul subway network where trains stop to allow passengers to board, alight, and transfer between lines and other modes of transportation.
-
B.
passenger rail service
chosen
Passenger rail service is a transportation system that operates trains to carry people between locations on a scheduled basis, typically offering various classes of comfort and amenities.
-
C.
public railway
A public railway is a government- or publicly-owned rail transport system that provides scheduled passenger and/or freight services accessible to the general population, typically operating on standardized tracks and infrastructure.
-
D.
rail transport company
A rail transport company is an organization that owns, operates, or manages trains and railway infrastructure to provide freight and/or passenger transportation services.
-
E.
high-speed rail service brand
A high-speed rail service brand is a distinct identity and marketing concept that represents a specific provider’s fast, long-distance passenger train services, encompassing its name, visual design, service standards, and customer experience.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:16 p.m.