Triple
T38344478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WHEELS (Livermore Amador Valley Transit Authority) |
E1041501
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transport organization in California |
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: transport organization in California Context triple: [WHEELS (Livermore Amador Valley Transit Authority), instanceOf, transport organization in California]
-
A.
transportation organization
A transportation organization is an entity that plans, manages, and operates systems or services that move people or goods from one location to another.
-
B.
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.
-
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.
paratransit operator
A paratransit operator is a transportation service provider that offers flexible, demand-responsive rides—often door-to-door—for individuals whose disabilities or mobility limitations prevent them from using standard public transit.
-
E.
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.
- 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.