Triple
T28532716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title X of the Public Health Service Act |
E722084
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | family planning program |
C10459
|
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: family planning program Context triple: [Title X of the Public Health Service Act, instanceOf, family planning program]
-
A.
family-centered service plan
A family-centered service plan is a coordinated, individualized roadmap of supports and interventions developed collaboratively with a family to address their unique needs, goals, and strengths across home, school, and community settings.
-
B.
family management system
A family management system is a centralized platform that helps households coordinate schedules, tasks, finances, and communication to streamline daily family life and responsibilities.
-
C.
public health program
chosen
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.
-
D.
reproductive rights legislation
Reproductive rights legislation encompasses laws and policies that regulate individuals’ access to reproductive healthcare, including contraception, abortion, fertility treatments, and related medical and informational services.
-
E.
family pooling program
A family pooling program is a system that allows multiple family members to combine and share resources, benefits, or usage limits (such as points, data, or credits) under a single collective account.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:29 a.m.