Triple
T28173618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Toronto |
E715529
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former upper-tier municipal government |
C40868
|
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: former upper-tier municipal government Context triple: [Metropolitan Toronto, instanceOf, former upper-tier municipal government]
-
A.
former municipal government
chosen
A former municipal government is a previously existing local governing body or administrative authority that has been dissolved, merged, or replaced and no longer exercises official jurisdiction over its former municipality.
-
B.
former local municipality
A former local municipality is an administrative area that once had its own local government authority but has since been dissolved, merged, or restructured into a different governing entity.
-
C.
former seat of local government
A former seat of local government is a building or location that previously served as the primary administrative center for a local governing authority but no longer holds that official function.
-
D.
former rural municipality
A former rural municipality is a previously independent local administrative unit in a countryside or non-urban area that has since been dissolved, merged, or reorganized into another jurisdiction.
-
E.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:14 p.m.