Triple
T13295687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Social Security Amendments of 1983 |
E316675
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Social Security reform |
C2631
|
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: Social Security reform Context triple: [Social Security Amendments of 1983, instanceOf, Social Security reform]
-
A.
social security benefit
A social security benefit is a government-provided payment or service intended to support individuals’ income, health, or well-being in situations such as retirement, disability, unemployment, or low income.
-
B.
New Deal reform
New Deal reform refers to the series of U.S. federal programs, regulations, and public works initiatives launched in the 1930s to provide relief, recovery, and long-term economic and social reform in response to the Great Depression.
-
C.
labor market reform
Labor market reform is the process of changing laws, regulations, and institutions governing employment to improve efficiency, flexibility, equity, or job creation in an economy.
-
D.
German welfare reform
German welfare reform refers to the ongoing process of restructuring Germany’s social security, labor market, and income support systems to balance social protection with economic efficiency and fiscal sustainability.
-
E.
social welfare legislation
chosen
Social welfare legislation comprises laws and policies enacted by governments to provide financial assistance, services, and protections aimed at improving the well-being and security of individuals and communities, particularly those who are vulnerable or disadvantaged.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:28 p.m.