Triple
T9288768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prospectus Regulation Rules |
E223463
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UK financial regulation |
C27140
|
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: UK financial regulation Context triple: [Prospectus Regulation Rules, instanceOf, UK financial regulation]
-
A.
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.
-
B.
European Union regulation
A European Union regulation is a binding legislative act that applies directly and uniformly in all EU member states without needing national implementing measures, establishing common rules and standards across the Union.
-
C.
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.
-
D.
banking law
Banking law is the body of legal rules and regulations that governs the creation, operation, and supervision of banks and other financial institutions, as well as their relationships with customers, regulators, and markets.
-
E.
financial reform
Financial reform is the process of redesigning laws, regulations, and institutions in the financial system to improve stability, fairness, transparency, and economic efficiency.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:35 p.m.