Triple
T4334272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Manchester Strategy |
E97425
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional development strategy |
C11489
|
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 strategy Context triple: [Greater Manchester Strategy, instanceOf, regional development strategy]
-
A.
regional strategy
chosen
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.
-
B.
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.
-
C.
regional transport plan
A regional transport plan is a strategic framework that outlines long-term goals, policies, and coordinated investments for transportation systems across a defined geographic region.
-
D.
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.
-
E.
European Union development strategy
The European Union development strategy is a coordinated framework of policies, funding instruments, and long-term goals designed to promote sustainable economic growth, social cohesion, environmental protection, and global partnerships within the EU and with partner countries.
- 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:14 p.m.