Triple
T7031191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maternal and Child Health Block Grant |
E163274
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public health funding program |
C357
|
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: public health funding program Context triple: [Maternal and Child Health Block Grant, instanceOf, public health funding program]
-
A.
public health program
A public health program is an organized set of coordinated activities and interventions designed to protect, promote, and improve the health of populations through prevention, education, policy, and services.
-
B.
public health security program
A public health security program is an organized set of policies, systems, and coordinated activities designed to prevent, detect, and respond to health threats that could impact the safety and well-being of populations.
-
C.
public health system
A public health system is the organized network of people, institutions, resources, and policies that work together to prevent disease, promote health, and protect the well-being of populations.
-
D.
World Health Organization program
A World Health Organization program is a coordinated global initiative designed and managed by WHO to address specific public health priorities through research, policy guidance, capacity building, and on-the-ground interventions in member states.
-
E.
federal government program
chosen
A federal government program is an organized set of activities, services, or regulations funded and administered by the national government to achieve specific public policy goals.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:35 p.m.