Triple
T1400009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Toronto Act, 2006 |
E30757
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | provincial statute |
C251
|
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: provincial statute Context triple: [City of Toronto Act, 2006, instanceOf, provincial statute]
-
A.
provincial order
A provincial order is a formal directive or regulation issued by a regional or provincial authority that governs specific activities, behaviors, or administrative procedures within its jurisdiction.
-
B.
statute
chosen
A statute is a formal written law enacted by a legislative body that establishes rules, obligations, or prohibitions within a governing jurisdiction.
-
C.
subnational legislature
A subnational legislature is a lawmaking body that operates below the national level—such as a state, provincial, or regional assembly—responsible for creating and overseeing laws and policies within its specific territorial jurisdiction.
-
D.
codified body of local laws
A codified body of local laws is an organized, authoritative collection of legal rules and regulations enacted by a specific local jurisdiction, such as a city or county, to govern conduct within its boundaries.
-
E.
constitutional statute
A constitutional statute is a fundamental law enacted by a legislature that, while formally an ordinary statute, has quasi-constitutional status because it implements, structures, or protects core constitutional principles and cannot be amended or repealed without special procedures or heightened scrutiny.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:59 p.m.