Triple
T37262099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid West Development Commission |
E924282
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional development commission |
C1090
|
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 development commission Context triple: [Mid West Development Commission, instanceOf, regional development commission]
-
A.
regional development fund
A regional development fund is a financial mechanism that pools and allocates resources to support economic growth, infrastructure, and social development projects within a specific geographic area.
-
B.
regional development programme
A regional development programme is a coordinated set of policies, investments, and initiatives designed to stimulate economic growth, improve infrastructure, and enhance social well-being within a specific geographic area.
-
C.
regional planning agency
chosen
A regional planning agency is an organization responsible for coordinating land use, transportation, infrastructure, and environmental planning across multiple jurisdictions within a defined geographic region.
-
D.
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.
-
E.
regional coordination unit
A regional coordination unit is an organizational entity responsible for aligning, integrating, and overseeing activities, resources, and communication across multiple local or sectoral actors within a defined geographic area.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.