Triple
T36686884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WKD |
E905840
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | suburban light rail system |
C5215
|
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 light rail system Context triple: [WKD, instanceOf, suburban light rail system]
-
A.
light rail transit line
chosen
A light rail transit line is a fixed-route urban or suburban rail corridor using electrically powered, relatively low-capacity trains that operate on dedicated or semi-exclusive tracks to provide frequent, short- to medium-distance passenger service.
-
B.
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.
-
C.
suburban railway corridor
A suburban railway corridor is a dedicated rail route connecting city centers with surrounding residential suburbs, designed to support frequent, high-capacity commuter train services.
-
D.
commuter rail line
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.
-
E.
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.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.