Triple
T12313940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ViaMobilidade lines |
E293550
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban rail service network |
C25581
|
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: urban rail service network Context triple: [ViaMobilidade lines, instanceOf, urban rail service network]
-
A.
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.
-
B.
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.
-
C.
commuter rail infrastructure
Commuter rail infrastructure comprises the physical and operational systems—such as tracks, stations, signaling, power, and maintenance facilities—designed to support frequent, reliable passenger train service between suburbs and urban centers.
-
D.
rapid transit line
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.
-
E.
group of rapid transit lines
chosen
A group of rapid transit lines is a collection of interconnected high-capacity urban rail or metro routes that operate together as a coordinated network to provide frequent, efficient public transportation.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:53 p.m.