Triple
T7053662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Health and Human Services Agency |
E164031
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | umbrella health and human services agency |
C6030
|
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: umbrella health and human services agency Context triple: [California Health and Human Services Agency, instanceOf, umbrella health and human services agency]
-
A.
umbrella organisation
chosen
An umbrella organisation is a central body that unites, coordinates, and represents multiple related groups or entities under a common structure or purpose.
-
B.
public social services agency
A public social services agency is a government-funded organization that provides assistance, protection, and support programs to individuals and families in need to promote their well-being and social stability.
-
C.
public health partnership
A public health partnership is a collaborative alliance among governmental agencies, community organizations, healthcare providers, and other stakeholders that coordinates resources and efforts to improve population health outcomes and address public health challenges.
-
D.
emergency management agency
An emergency management agency is an organization responsible for preparing for, coordinating, and responding to natural or human-made disasters to protect people, property, and the environment.
-
E.
health authority
A health authority is an organization or governmental body responsible for overseeing, regulating, and coordinating public health services, policies, and programs within a specific jurisdiction.
- 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_69c68861678881909961ddf4d779f750 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:37 p.m.