Triple
T4634141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco Office of the Budget and Legislative Analyst |
E101487
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nonpartisan legislative support office |
C1316
|
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: nonpartisan legislative support office Context triple: [San Francisco Office of the Budget and Legislative Analyst, instanceOf, nonpartisan legislative support office]
-
A.
nonpartisan legislative office
chosen
A nonpartisan legislative office is an organizational unit within a legislative body that provides neutral, fact-based research, analysis, and administrative support to all members regardless of political affiliation.
-
B.
nonpartisan agency
A nonpartisan agency is an organization that conducts its work and makes decisions without aligning with or favoring any political party or ideological agenda.
-
C.
office of the United States Congress
An office of the United States Congress is an organizational unit within the legislative branch that supports the operations, administration, or policymaking functions of the House of Representatives, the Senate, or their joint activities.
-
D.
parliamentary service
Parliamentary service is the professional support and administrative work carried out to assist a parliament in its legislative, oversight, and representative functions.
-
E.
party department
A party department is an organizational unit within a political party responsible for managing specific functions such as policy development, communications, membership, or campaign operations.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:13 p.m.