Triple
T28531259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1977 San Francisco Board of Supervisors election |
E722047
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | San Francisco Board of Supervisors election |
C54212
|
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 Board of Supervisors election Context triple: [1977 San Francisco Board of Supervisors election, instanceOf, San Francisco Board of Supervisors election]
-
A.
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.
-
B.
district of San Francisco
A district of San Francisco is a geographically defined area within the city that groups neighborhoods sharing common administrative boundaries, local services, and community characteristics.
-
C.
California state election
A California state election is a formal, statewide process in which eligible voters in California choose public officials, decide on ballot measures, and influence state governance according to established electoral laws and procedures.
-
D.
California ballot proposition
A California ballot proposition is a proposed law or constitutional amendment placed before California voters for approval or rejection in a statewide election.
-
E.
Berkeley City Council district
A Berkeley City Council district is a defined geographic area within the City of Berkeley that elects one representative to serve on the Berkeley City Council.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:28 a.m.