Triple
T37267847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muni 5 Fulton |
E924434
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | San Francisco Municipal Railway route |
C64084
|
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: San Francisco Municipal Railway route Context triple: [Muni 5 Fulton, instanceOf, San Francisco Municipal Railway route]
-
A.
San Francisco Municipal Railway facility
A San Francisco Municipal Railway facility is a physical site used for the operation, maintenance, storage, and administration of Muni transit vehicles and related services within the San Francisco public transportation system.
-
B.
San Diego Trolley line
A San Diego Trolley line is a specific light rail route within the San Diego Metropolitan Transit System that operates along a defined corridor, serving designated stations according to a published schedule.
-
C.
Los Angeles Metro Busway line
A Los Angeles Metro Busway line is a high-capacity, limited-stop bus service operating primarily on dedicated busways or managed lanes to provide faster, more reliable transit across key corridors in the Los Angeles metropolitan area.
-
D.
DC Circulator line
A DC Circulator line is a specific bus route within Washington, D.C.’s Circulator transit system that provides frequent, low-cost service along a defined corridor connecting key neighborhoods and destinations.
-
E.
TEXRail station
A TEXRail station is a designated passenger rail facility along the TEXRail commuter line that provides platforms, ticketing access, and related amenities for boarding and alighting TEXRail trains.
- F. None of above. chosen
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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.