Triple
T23665981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Railroad Retirement Act |
E584577
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | social insurance law |
C47930
|
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 insurance law Context triple: [Railroad Retirement Act, instanceOf, social insurance law]
-
A.
social welfare legislation
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.
-
B.
labor law
Labor law is the body of rules and principles governing the rights, duties, and relationships between employers, employees, and labor organizations in the workplace.
-
C.
health insurance law
Health insurance law is the body of legal rules and regulations that governs the creation, coverage, administration, and enforcement of health insurance policies and the rights and obligations of insurers, providers, and insured individuals.
-
D.
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.
-
E.
employee benefits law
Employee benefits law governs the creation, administration, and regulation of employer-sponsored benefit plans—such as health insurance, retirement, and disability programs—ensuring compliance with legal standards and protection of employees’ rights.
- F. None of above. chosen
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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:50 p.m.