Triple
T4686718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Capital Region Planning Board |
E103937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional planning authority |
C1090
|
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 authority Context triple: [National Capital Region Planning Board, instanceOf, regional planning authority]
-
A.
regional planning agency
chosen
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.
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.
-
C.
independent regional agency
An independent regional agency is an autonomous public or quasi-public organization that operates within a specific geographic region to plan, coordinate, and deliver specialized services or regulatory functions separate from direct control by central government bodies.
-
D.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
E.
planned regional parliament
A planned regional parliament is a proposed legislative body intended to represent and govern a specific geographic region, but which has not yet been formally established or begun operation.
- 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_69bd43debbf08190b4bc372e286ec234 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:16 p.m.