Triple
T32308071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Code of Social Security |
E825420
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | social security treaty |
C566
|
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 treaty Context triple: [European Code of Social Security, instanceOf, social security treaty]
-
A.
social security coordination rules
Social security coordination rules are legal provisions that determine how different countries’ social security systems interact to ensure individuals moving across borders receive continuous and fair coverage without double contributions or benefit gaps.
-
B.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
C.
social insurance law
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 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.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:45 a.m.