Triple
T23098125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BART Red Line |
E575950
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | BART service pattern |
C20256
|
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: BART service pattern Context triple: [BART Red Line, instanceOf, BART service pattern]
-
A.
railway line service pattern
chosen
A railway line service pattern defines the structured arrangement of train services over a route, including stopping sequences, frequencies, and service types that determine how trains operate along the line.
-
B.
bus service network
A bus service network is an interconnected system of bus routes, stops, schedules, and vehicles designed to transport passengers efficiently across a defined geographic area.
-
C.
San Francisco Muni service application
A San Francisco Muni service application is a mobile or web-based system that provides real-time transit information, trip planning, service alerts, and fare-related features for riders using San Francisco’s Muni public transportation network.
-
D.
rapid transit line segment
A rapid transit line segment is a contiguous portion of a rapid transit route between two defined points (such as stations, junctions, or terminals) that carries high-frequency, high-capacity passenger rail service.
-
E.
fixed-route transit service
Fixed-route transit service is a public transportation mode that operates vehicles along predetermined paths with scheduled stops and timetables, regardless of individual passenger requests.
- 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_69e245c060b48190a9bd61a47a16db17 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:57 p.m.