Triple
T34036534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keihan network between Osaka and Kyoto |
E872813
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intercity rail system |
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: intercity rail system Context triple: [Keihan network between Osaka and Kyoto, instanceOf, intercity rail system]
-
A.
intercity passenger rail project
An intercity passenger rail project is a coordinated planning, design, and construction effort to develop or improve rail infrastructure and services that transport people efficiently between cities over medium to long distances.
-
B.
rapid rail system
A rapid rail system is a high-speed, high-capacity railway network designed to transport large numbers of passengers quickly and efficiently between urban or regional destinations using dedicated tracks and frequent service.
-
C.
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.
-
D.
private railway
A private railway is a rail transport system owned and operated by a non-governmental entity, typically for exclusive use in serving specific industrial, commercial, or regional transportation needs.
-
E.
high-speed railway
A high-speed railway is a rail transport system designed for trains that operate at significantly higher speeds than traditional rail services, typically on specially built or upgraded tracks, to provide fast, efficient, and reliable long-distance passenger travel.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:51 a.m.