Triple
T15969618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 4 (Culver CityBus) |
E387285
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transit bus route |
C2036
|
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 bus route Context triple: [Line 4 (Culver CityBus), instanceOf, public transit bus route]
-
A.
public transit route
chosen
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.
-
B.
local bus route
A local bus route is a designated path within a limited geographic area along which buses operate on a regular schedule to transport passengers between specific stops.
-
C.
public transit board
A public transit board is a governing body responsible for overseeing, setting policy for, and making strategic decisions about a region’s public transportation system.
-
D.
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.
-
E.
public transit plan
A public transit plan is a structured strategy that outlines routes, schedules, resources, and policies to provide efficient, accessible, and sustainable transportation services within a community or region.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:54 a.m.