Triple
T19155851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pension Fund of Ukraine |
E468925
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pension authority |
C36223
|
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 authority Context triple: [Pension Fund of Ukraine, instanceOf, pension authority]
-
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 fund service provider
A pension fund service provider is an organization that offers administrative, investment, compliance, and advisory services to pension funds to help manage their assets, operations, and regulatory obligations.
-
C.
occupation authority section
An occupation authority section is a designated part of a document or system that defines, records, and manages the official powers, responsibilities, and permissions associated with a specific job or role.
-
D.
national social insurance institution
chosen
A national social insurance institution is a government-established organization responsible for administering mandatory social protection programs such as pensions, unemployment benefits, health insurance, and disability support for a country’s residents.
-
E.
public benefits administrator
A public benefits administrator oversees the implementation, management, and compliance of government assistance programs to ensure eligible individuals and families receive appropriate services and support.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:06 p.m.