Triple
T3347087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol Corridor Joint Powers Authority |
E70401
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional rail authority |
C220
|
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: regional rail authority Context triple: [Capitol Corridor Joint Powers Authority, instanceOf, regional rail authority]
-
A.
public transportation agency
chosen
A public transportation agency is an organization responsible for planning, operating, and managing shared transit services such as buses, trains, and other modes to provide mobility for the public within a defined region.
-
B.
rapid transit division
A rapid transit division is an organizational unit within a transportation agency responsible for planning, operating, and maintaining high-frequency, high-capacity urban rail or bus rapid transit services.
-
C.
mass transit operator
A mass transit operator is an entity responsible for managing, coordinating, and providing public transportation services such as buses, trains, or subways within a specific region or network.
-
D.
commuter rail station
A commuter rail station is a designated facility where passengers board and alight regional trains that connect suburbs or outlying areas with urban centers, typically offering platforms, ticketing, and basic passenger amenities.
-
E.
commuter rail line
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.
- 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_69ad85a4ef7c8190a29e2bbd6fa454e4 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:12 p.m.