Triple
T38073428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Social Code Book VI |
E950645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pension insurance statute |
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: pension insurance statute Context triple: [Social Code Book VI, instanceOf, pension insurance statute]
-
A.
pension plan
A pension plan is a long-term savings and investment arrangement, typically sponsored by an employer or government, that provides individuals with regular income payments after retirement based on contributions and plan rules.
-
B.
pension board
A pension board is a governing body responsible for overseeing the management, investment, and administration of a pension fund to ensure benefits are properly funded and paid to eligible participants.
-
C.
social insurance law
chosen
Social insurance law is the body of legal rules and principles governing public programs that provide income support and benefits—such as pensions, unemployment, disability, and health coverage—to protect individuals against social and economic risks.
-
D.
social insurance parameter
A social insurance parameter is a configurable policy variable that defines specific rules, thresholds, or rates governing how social insurance programs calculate contributions, eligibility, and benefits.
-
E.
pensions regulator
A pensions regulator is an authority or agency responsible for overseeing pension schemes to ensure they are run safely, fairly, and in compliance with legal and financial standards to protect members’ retirement benefits.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.