Triple
T4972946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council for Finance and Planning |
E111697
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional economic policy body |
C11923
|
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 economic policy body Context triple: [Council for Finance and Planning, instanceOf, regional economic policy body]
-
A.
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.
-
B.
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.
-
C.
regional body of an international organization
chosen
A regional body of an international organization is a geographically focused subdivision that implements the organization’s policies, coordinates activities, and represents its interests within a specific region.
-
D.
international economic organization
An international economic organization is an institution formed by multiple countries to coordinate and regulate economic policies, trade, finance, and development across national borders.
-
E.
regional organisation of councils
A regional organisation of councils is a collaborative body formed by multiple local government councils within a geographic region to coordinate planning, share resources, and advocate on common regional issues.
- 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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:33 p.m.