Triple
T281038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J |
E5354
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rapid transit service |
C640
|
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: rapid transit service Context triple: [J, instanceOf, rapid transit service]
-
A.
rapid transit line
chosen
A rapid transit line is a high-capacity, high-frequency urban rail route operating on an exclusive or mostly separated right-of-way to provide fast, reliable public transportation between key areas of a city or metropolitan region.
-
B.
passenger rail service
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.
-
C.
rail transit
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.
-
D.
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.
-
E.
rapid transit station
A rapid transit station is a designated facility where passengers board, alight, and transfer between high-frequency urban rail or metro services, typically featuring platforms, ticketing areas, and access to surrounding streets or other transport modes.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.