Triple

T23353436
Position Surface form Disambiguated ID Type / Status
Subject Trading and Markets Division E592979 entity
Predicate instanceOf P0 FINISHED
Object financial regulatory authority division C37101 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 authority division
Context triple: [Trading and Markets Division, instanceOf, financial regulatory authority division]
  • 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. 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.
  • C. 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.
  • D. banking division
    A banking division is an organizational unit within a financial institution responsible for managing specific banking services, customer segments, or product lines to achieve targeted financial and strategic objectives.
  • E. regulatory agency component chosen
    A regulatory agency component is a modular part of a regulatory body responsible for performing specific oversight, rulemaking, enforcement, or compliance functions within a defined domain.
  • 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_69e25d24d2a4819092e6ede74c2a918d completed April 17, 2026, 4:17 p.m.
Created at: April 17, 2026, 5:20 p.m.