Triple
T29560807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ST3 |
E750033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sound Transit ballot measure |
C25454
|
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: Sound Transit ballot measure Context triple: [ST3, instanceOf, Sound Transit ballot measure]
-
A.
municipal ballot measure
A municipal ballot measure is a proposed law, policy, or funding decision placed before voters in a city or local jurisdiction for direct approval or rejection in an election.
-
B.
transportation funding measure
chosen
A transportation funding measure is a policy instrument, often a ballot initiative or legislative act, that authorizes and allocates dedicated revenue sources to plan, build, operate, and maintain transportation infrastructure and services.
-
C.
Los Angeles County ballot measure
A Los Angeles County ballot measure is a proposed law, policy change, or funding decision specific to Los Angeles County that is placed before county voters for approval or rejection in an election.
-
D.
San Francisco Board of Supervisors election
The San Francisco Board of Supervisors election is a local governmental contest in which voters choose representatives for the city's legislative body, determining policy direction and neighborhood representation.
-
E.
Los Angeles Metro project
The Los Angeles Metro project is a large-scale public transportation initiative focused on expanding and improving the region’s rail and bus networks to enhance mobility, reduce congestion, and support sustainable urban growth across Los Angeles County.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 5:19 p.m.