Triple
T31836521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco Health Commission |
E812688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health policy-making body |
C172
|
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: health policy-making body Context triple: [San Francisco Health Commission, instanceOf, health policy-making body]
-
A.
health policy department
A health policy department is an organizational unit responsible for researching, developing, analyzing, and advising on policies that shape healthcare systems, public health initiatives, and regulatory frameworks.
-
B.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
C.
science policy coordination body
A science policy coordination body is an organization that aligns scientific research, evidence, and expertise with policymaking processes across institutions and sectors to ensure coherent, informed, and effective public policy.
-
D.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
E.
central policymaking organ
A central policymaking organ is the primary authoritative body within an organization or state responsible for formulating, coordinating, and directing overarching policies and strategic decisions.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:48 p.m.