Triple
T7223294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macon Area Transportation Study MPO |
E150313
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Metropolitan planning organization |
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: Metropolitan planning organization Context triple: [Macon Area Transportation Study MPO, instanceOf, Metropolitan planning organization]
-
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.
metropolitan authority
A metropolitan authority is a governing body responsible for planning, coordinating, and managing public services and development across a large urban area and its surrounding municipalities.
-
C.
Mayoral development corporation
A mayoral development corporation is a public body established by a city’s mayor to lead and coordinate regeneration, planning, and economic development within a designated urban area.
-
D.
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.
-
E.
Micropolitan Statistical Area
A Micropolitan Statistical Area is a geographic region defined by the U.S. Office of Management and Budget centered around an urban core with a population between 10,000 and 49,999, plus adjacent territories with strong social and economic integration.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:54 p.m.