Triple
T28828160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narita International Airport rail access system |
E727968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway transport network |
C3549
|
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: railway transport network Context triple: [Narita International Airport rail access system, instanceOf, railway transport network]
-
A.
railway network
chosen
A railway network is an interconnected system of tracks, stations, signaling, and rolling stock that enables the organized movement of trains between multiple locations.
-
B.
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.
-
C.
rail transportation infrastructure
Rail transportation infrastructure encompasses the physical and organizational systems—such as tracks, stations, signaling, power supply, and related facilities—required to support the safe and efficient movement of trains and rail-based services.
-
D.
freight railroad network
A freight railroad network is an interconnected system of rail lines, terminals, and supporting infrastructure designed to transport goods and raw materials efficiently between industrial, commercial, and logistical hubs.
-
E.
national railway system
A national railway system is a coordinated network of rail infrastructure, services, and governance that provides passenger and freight transportation across a country.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:36 a.m.