Triple
T25254174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCBG |
E633122
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional monetary policy 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: regional monetary policy coordination body Context triple: [CCBG, instanceOf, regional monetary policy coordination body]
-
A.
planned regional monetary fund
A planned regional monetary fund is a proposed financial institution designed to pool resources from member countries within a specific region to provide monetary stability, balance-of-payments support, and coordinated economic policies.
-
B.
monetary policy region
A monetary policy region is a geographic or economic area within which a single monetary authority implements a unified set of monetary policy tools and rules, typically sharing a common currency and interest rate framework.
-
C.
regional development bank
A regional development bank is a multilateral financial institution that provides loans, grants, and technical assistance to support economic and social development within a specific geographic region.
-
D.
financial regulatory coordination body
chosen
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.
-
E.
regional cooperation bloc
A regional cooperation bloc is an alliance of neighboring countries that coordinate policies and collaborate on economic, political, or security issues to advance shared regional interests.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:12 p.m.