Triple
T4894198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FSOC |
E109633
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial regulatory coordination body |
C16586
|
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: financial regulatory coordination body Context triple: [FSOC, instanceOf, financial regulatory coordination body]
-
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.
regulatory authority
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.
self-regulatory organization
A self-regulatory organization is an entity, typically within a specific industry or profession, that creates and enforces rules and standards for its members to promote fair, ethical, and orderly conduct, often under the oversight of a governmental authority.
-
D.
financial oversight office
A financial oversight office is an organizational unit responsible for monitoring, reviewing, and ensuring the accuracy, compliance, and integrity of an entity’s financial activities and reporting.
-
E.
financial market infrastructure company
A financial market infrastructure company provides the core systems, platforms, and services that enable the trading, clearing, settlement, and reporting of financial instruments in a safe, efficient, and regulated manner.
- 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:28 p.m.