Triple
T10993537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shared Vision Program |
E259806
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional program |
C18913
|
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 program Context triple: [Shared Vision Program, instanceOf, regional program]
-
A.
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.
-
B.
regional development programme
chosen
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 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.
community-based program
A community-based program is an organized set of activities and services designed and delivered within a local community to address shared needs, build capacity, and improve well-being through active resident participation and local partnerships.
-
E.
regional institute
A regional institute is an organization dedicated to education, research, or specialized services that primarily serves and addresses the needs of a specific geographic area or 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:24 p.m.