Triple
T10999590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of the Superintendent of Bankruptcy Canada |
E259970
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | insolvency 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: insolvency regulator Context triple: [Office of the Superintendent of Bankruptcy Canada, instanceOf, insolvency regulator]
-
A.
bankruptcy trustee
A bankruptcy trustee is a court-appointed fiduciary responsible for administering a debtor’s bankruptcy estate, liquidating or managing assets, and distributing proceeds fairly to creditors in accordance with bankruptcy law.
-
B.
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.
-
C.
court-appointed trustee
A court-appointed trustee is a neutral third party designated by a court to manage, protect, and administer assets or affairs on behalf of beneficiaries or creditors in accordance with legal and fiduciary duties.
-
D.
financial regulatory authority
A financial regulatory authority is an organization empowered by law to oversee, supervise, and enforce rules governing financial markets and institutions to ensure stability, integrity, and consumer protection.
-
E.
financial regulatory coordination body
A financial regulatory coordination body is an organization that facilitates collaboration, information-sharing, and policy alignment among multiple financial regulators to promote consistent oversight, reduce systemic risk, and address cross-border or cross-sector regulatory issues.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:25 p.m.