Triple
T4061762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Railway suburban network |
E86228
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | suburban railway system |
C74
|
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: suburban railway system Context triple: [Moscow Railway suburban network, instanceOf, suburban railway system]
-
A.
suburban commuter train
A suburban commuter train is a passenger rail service designed to transport people efficiently between residential suburbs and urban centers, typically operating on fixed schedules with frequent stops during peak travel times.
-
B.
commuter rail line
chosen
A commuter rail line is a passenger train service that operates on fixed tracks and schedules to connect suburban or outlying areas with a central city, primarily serving daily work and school commuters.
-
C.
urban rail loop line
An urban rail loop line is a circular or near-circular transit route within a city that connects multiple districts and intersecting lines, allowing continuous, bidirectional travel without a terminal endpoint.
-
D.
streetcar system
A streetcar system is an urban public transit network that operates rail vehicles on fixed tracks, typically embedded in city streets, to transport passengers along defined routes.
-
E.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:38 p.m.