Triple
T37789403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSRS Offset |
E942039
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hybrid retirement system |
C7279
|
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: hybrid retirement system Context triple: [CSRS Offset, instanceOf, hybrid retirement system]
-
A.
pension plan
chosen
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.
hybrid work
Hybrid work is a flexible employment model in which employees split their time between remote locations and a central workplace, balancing in-person collaboration with the autonomy of working from anywhere.
-
C.
multiemployer benefit plan
A multiemployer benefit plan is a collectively bargained employee benefit arrangement maintained by two or more unrelated employers, typically within the same industry, and administered by a joint board of trustees representing both employers and labor unions.
-
D.
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.
-
E.
hybrid energy recovery system
A hybrid energy recovery system is an integrated setup that captures, stores, and reuses waste energy from multiple sources (such as mechanical, thermal, and electrical) to improve overall efficiency and reduce primary energy consumption.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.