Triple
T30378779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles Metro Rail C Line stations |
E772764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rapid transit stations collection |
C24861
|
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 stations collection Context triple: [Los Angeles Metro Rail C Line stations, instanceOf, rapid transit stations collection]
-
A.
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.
-
B.
bus rapid transit station group
A bus rapid transit station group is a coordinated set of closely spaced BRT stations or platforms that function together as a single operational unit to serve high-capacity, high-frequency bus services along a corridor.
-
C.
rapid transit depot
A rapid transit depot is a specialized facility where urban rail vehicles are stored, inspected, maintained, and dispatched for service on a rapid transit network.
-
D.
group of metro interchange stations
A group of metro interchange stations is a collection of transit hubs where multiple metro lines intersect, enabling passengers to transfer between routes within an urban rail network.
-
E.
group of railway stations
chosen
A group of railway stations is a conceptual collection of multiple train stations considered together for purposes such as management, analysis, planning, or classification within a rail network.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8 p.m.