Triple
T16070465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cocopah Health and Human Services |
E389847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health and human services department |
C14602
|
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 and human services department Context triple: [Cocopah Health and Human Services, instanceOf, health and human services department]
-
A.
division of the United States Department of Health and Human Services
A division of the United States Department of Health and Human Services is an organizational unit within HHS responsible for administering specific health, human services, or regulatory programs in support of the department’s overall mission.
-
B.
health agency
A health agency is an organization responsible for planning, coordinating, and delivering public health services, policies, and programs to protect and improve the health of a population.
-
C.
health ministry
A health ministry is a governmental body responsible for formulating and implementing public health policies, managing healthcare systems, and safeguarding the population’s health and well-being.
-
D.
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.
-
E.
public social services agency
chosen
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.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:57 a.m.