Triple
T8970970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Development Goals |
E214264
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-poverty initiative |
C18701
|
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: anti-poverty initiative Context triple: [International Development Goals, instanceOf, anti-poverty initiative]
-
A.
War on Poverty initiative
The War on Poverty initiative is a coordinated set of government programs and policies aimed at reducing poverty and improving economic opportunity for disadvantaged populations.
-
B.
development initiative
chosen
A development initiative is a coordinated set of actions and resources aimed at improving social, economic, or environmental conditions within a specific community, sector, or region.
-
C.
pastoral initiative
A pastoral initiative is an organized effort within a faith or church community designed to address specific spiritual, social, or pastoral needs through targeted programs, activities, or ministries.
-
D.
public housing subsidy program
A public housing subsidy program is a government initiative that provides financial assistance or reduced-cost housing to eligible low-income individuals and families to ensure access to safe, stable, and affordable homes.
-
E.
economic aid program
An economic aid program is an organized initiative, typically funded by governments or international institutions, designed to provide financial resources, technical assistance, or policy support to stimulate economic development, stabilize economies, or alleviate poverty in targeted regions or populations.
- 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:02 p.m.