Triple

T1491783
Position Surface form Disambiguated ID Type / Status
Subject Metropolitan Council E29595 entity
Predicate instanceOf P0 FINISHED
Object regional 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: regional planning organization
Context triple: [Metropolitan Council, instanceOf, regional 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. regional organisation of councils
    A regional organisation of councils is a collaborative body formed by multiple local government councils within a geographic region to coordinate planning, share resources, and advocate on common regional issues.
  • 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 center
    A regional center is an organization or facility that provides specialized services, coordination, and support to a defined geographic area, often acting as a hub for resources, administration, or expertise.
  • E. 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.
  • 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_69a498da82e08190ba833330d05f380f completed March 1, 2026, 7:51 p.m.
Created at: March 1, 2026, 8:12 p.m.