Triple
T7750061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto City Council procedural by-law |
E175733
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal procedural by-law |
C5720
|
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: municipal procedural by-law Context triple: [Toronto City Council procedural by-law, instanceOf, municipal procedural by-law]
-
A.
municipal ordinance
chosen
A municipal ordinance is a local law or regulation enacted by a city or town government to govern conduct, land use, public safety, and other matters within its jurisdiction.
-
B.
municipal board
A municipal board is a local governing body composed of appointed or elected members responsible for making decisions, setting policies, and overseeing specific functions or services within a municipality.
-
C.
municipal enabling act
A municipal enabling act is a statute passed by a higher level of government that grants municipalities the legal authority and powers necessary to govern and regulate local affairs.
-
D.
municipal program
A municipal program is an organized set of services, initiatives, or activities implemented and managed by a local government to address community needs and improve public welfare within its jurisdiction.
-
E.
municipal property
Municipal property is any land, buildings, infrastructure, or other assets owned, leased, or otherwise controlled by a local government for public use or municipal operations.
- 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_69c69960b3588190a53aa590d31d9544 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 4:08 p.m.