Triple
T14271420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alameda/Oakland–San Francisco route |
E353793
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commuter transport service |
C74
|
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: commuter transport service Context triple: [Alameda/Oakland–San Francisco route, instanceOf, commuter transport service]
-
A.
transportation service
A transportation service is a system or business that moves people or goods from one location to another using various modes of transport under defined schedules, routes, and conditions.
-
B.
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.
-
C.
commuter rail line
chosen
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.
-
D.
public transport service feature
A public transport service feature is a specific characteristic, function, or amenity of a public transportation offering that affects how passengers access, experience, and evaluate the service.
-
E.
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.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:10 a.m.