Triple
T5325256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Self-Sufficiency Program for participating families |
E121769
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | HUD-supported initiative |
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: HUD-supported initiative Context triple: [Family Self-Sufficiency Program for participating families, instanceOf, HUD-supported initiative]
-
A.
Hewlett Foundation initiative
A Hewlett Foundation initiative is a strategic, time-bound program of philanthropic activities designed to address specific social, environmental, or educational challenges aligned with the foundation’s mission.
-
B.
Hewlett Foundation program
A Hewlett Foundation program is a structured philanthropic initiative designed and funded by the William and Flora Hewlett Foundation to address specific social, environmental, or educational challenges through grants and strategic partnerships.
-
C.
state-run initiative
A state-run initiative is a government-organized and funded program or project designed to achieve specific public policy goals or deliver services to citizens.
-
D.
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.
-
E.
World Bank fund
A World Bank fund is a financial mechanism established by the World Bank to pool and allocate resources for development projects and programs aimed at reducing poverty and promoting sustainable economic growth in member countries.
- 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_69bd463d956c819088105c3db802c017 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 1:59 p.m.