Triple
T37310634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri State Employees’ Retirement System board |
E926196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public 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: public pension board Context triple: [Missouri State Employees’ Retirement System board, instanceOf, public pension board]
-
A.
pension board
chosen
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
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.
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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.