Triple
T25256808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pension Fund Regulatory and Development Authority |
E633193
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pension regulator |
C1181
|
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 regulator Context triple: [Pension Fund Regulatory and Development Authority, instanceOf, pension regulator]
-
A.
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.
-
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.
regulatory authority
chosen
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
-
D.
financial services regulation
Financial services regulation encompasses the laws, rules, and supervisory frameworks that govern financial institutions and markets to ensure stability, integrity, consumer protection, and fair competition.
-
E.
legal services regulator
A legal services regulator is an authority responsible for overseeing, licensing, and enforcing standards of conduct and competence among legal service providers to protect the public interest and maintain confidence in the legal system.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:13 p.m.