Triple
T19490653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urban agglomeration of Montreal |
E487639
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | metropolitan governance entity |
C16436
|
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 governance entity Context triple: [Urban agglomeration of Montreal, instanceOf, metropolitan governance entity]
-
A.
metropolitan authority
chosen
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.
-
B.
local governmental entity
A local governmental entity is an administrative organization, such as a city, county, or district, that exercises governmental authority and provides public services within a specific geographic area below the level of the central or national government.
-
C.
governance entity
A governance entity is an individual, group, or organization with the authority and responsibility to establish, oversee, and enforce rules, policies, and decisions within a defined domain.
-
D.
metropolitan province
A metropolitan province is a large administrative region that encompasses a major city and its surrounding urban and suburban areas, functioning as a unified political and economic unit.
-
E.
centrally governed city
A centrally governed city is an urban area whose key administrative, economic, and policy decisions are directed and controlled by a single, central authority rather than by multiple local or decentralized bodies.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:39 p.m.