Triple
T3670931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alliance for Prosperity |
E77876
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional development initiative |
C11426
|
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 initiative Context triple: [Alliance for Prosperity, instanceOf, regional development initiative]
-
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.
planned regional development bank
A planned regional development bank is a proposed financial institution designed to mobilize and allocate long-term capital within a specific geographic region to support sustainable economic growth, infrastructure, and social development projects.
-
C.
regional strategy
A regional strategy is a coordinated plan that aligns resources, initiatives, and policies to achieve specific objectives within a defined geographic area, considering its unique economic, cultural, and competitive context.
-
D.
regional partnership
chosen
A regional partnership is a collaborative alliance among organizations, governments, or stakeholders within a specific geographic area to coordinate resources, strategies, and initiatives toward shared economic, social, or environmental goals.
-
E.
regional planning agency
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.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:25 p.m.