Triple
T8040775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer Valley Planning Commission |
E187429
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional planning commission |
C18700
|
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 planning commission Context triple: [Pioneer Valley Planning Commission, instanceOf, regional planning commission]
-
A.
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.
-
B.
planning commission
chosen
A planning commission is a governmental or advisory body responsible for reviewing, guiding, and making recommendations on land use, development proposals, and long-term community planning policies.
-
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 planner
A regional planner is a professional who analyzes and coordinates land use, infrastructure, resources, and policies across multiple communities or jurisdictions to guide sustainable and balanced regional development.
-
E.
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.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:23 p.m.