Triple
T5222192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domestic Marshall Plan for American cities |
E117895
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-poverty program proposal |
C1371
|
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 program proposal Context triple: [Domestic Marshall Plan for American cities, instanceOf, anti-poverty program proposal]
-
A.
social reform proposal
A social reform proposal is a structured plan or recommendation aimed at changing existing social policies, institutions, or practices to address perceived injustices or improve societal well-being.
-
B.
policy program
A policy program is a coordinated set of government or organizational initiatives, actions, and resources designed to achieve specific public or institutional goals through the implementation of formal policies.
-
C.
political proposal
chosen
A political proposal is a formally articulated plan or set of measures put forward by a political actor or group to address public issues, change policies, or introduce new legislation.
-
D.
domestic policy program
A domestic policy program is a coordinated set of government actions and initiatives designed to address specific national issues and objectives within a country’s borders.
-
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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:48 p.m.