Triple
T185097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autoriteit Financiële Markten |
E3963
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial regulatory authority |
C1299
|
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 Context triple: [Autoriteit Financiële Markten, instanceOf, financial regulatory authority]
-
A.
financial institution
A financial institution is an organization that manages money and financial services, such as accepting deposits, providing loans, facilitating investments, and enabling payment transactions for individuals, businesses, and governments.
-
B.
financial market
A financial market is a system or platform where buyers and sellers trade financial assets such as stocks, bonds, currencies, and derivatives, determining their prices through supply and demand.
-
C.
federal institution
A federal institution is an organization established and operated by a national government to implement, regulate, or support public policies and services across the entire country.
-
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.
component of the United States Department of the Treasury
A component of the United States Department of the Treasury is an organizational unit, such as a bureau, office, or service, that operates under the Department’s authority to carry out specific financial, regulatory, enforcement, or administrative functions of the federal government.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.