Triple
T32812733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Puget Sound Regional Transit Authority District |
E839200
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transit service district |
C42172
|
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: public transit service district Context triple: [Central Puget Sound Regional Transit Authority District, instanceOf, public transit service district]
-
A.
transit service area
chosen
A transit service area is the geographic region within which a public transportation provider offers routes, stops, and related services to riders.
-
B.
public transit station
A public transit station is a designated facility where passengers can access, board, transfer between, and disembark from public transportation services such as buses, trains, or subways.
-
C.
public transit route
A public transit route is a predefined path with designated stops and schedules along which public transportation vehicles (such as buses, trams, or trains) operate to move passengers between locations.
-
D.
public transit operations division
The public transit operations division is responsible for planning, scheduling, managing, and overseeing the daily operation and performance of a region’s public transportation services.
-
E.
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.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:15 a.m.