Triple
T28828159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Narita International Airport rail access system |
E727968
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airport rail access system |
C912
|
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: airport rail access system Context triple: [Narita International Airport rail access system, instanceOf, airport rail access system]
-
A.
airport rail station
An airport rail station is a transportation facility that directly connects an airport to regional or long-distance rail networks, enabling passengers to transfer efficiently between air and train travel.
-
B.
passenger rail terminal
A passenger rail terminal is a dedicated facility where travelers board, disembark, and transfer between trains, supported by platforms, ticketing, waiting areas, and related passenger services.
-
C.
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.
-
D.
rail transit
chosen
Rail transit is a public transportation system that moves passengers or freight along fixed steel tracks using trains, subways, trams, or light rail vehicles, typically in urban or intercity corridors.
-
E.
commuter rail fare system
A commuter rail fare system is a structured method for calculating, collecting, and validating payments for passengers traveling on regional rail services, typically based on zones, distance, or time of 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:36 a.m.