Triple
T28282177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Joint Staff Pension Board |
E713178
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pension board |
C53826
|
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 board Context triple: [United Nations Joint Staff Pension Board, instanceOf, pension board]
-
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.
CalPERS committee
A CalPERS committee is a specialized governing body within the California Public Employees’ Retirement System that oversees specific areas of policy, investment, or administration and makes recommendations or decisions to support the fund’s overall mission and fiduciary responsibilities.
-
D.
employee benefit plan
An employee benefit plan is an organized program established by an employer to provide workers with non-wage compensation such as health insurance, retirement savings, paid leave, and other benefits.
-
E.
CalPERS facility
A CalPERS facility is a physical or virtual location operated or designated by the California Public Employees’ Retirement System to support its administrative, investment, member service, or operational activities.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:23 p.m.