Triple
T8891939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Powerhouse |
E211700
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional policy initiative |
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 policy initiative Context triple: [Northern Powerhouse, instanceOf, regional policy initiative]
-
A.
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.
-
B.
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.
-
C.
regional planning program
A regional planning program is an organized framework of policies, strategies, and actions designed to guide the coordinated development, land use, infrastructure, and resource management of a specific geographic area over time.
-
D.
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.
-
E.
regional partnership
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.
- 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_69ca83907954819096d52a245b635841 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:54 p.m.