Triple
T6151408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto and Region Conservation Authority |
E137210
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conservation authority |
C11266
|
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: conservation authority Context triple: [Toronto and Region Conservation Authority, instanceOf, conservation authority]
-
A.
flood control agency
A flood control agency is an organization responsible for planning, implementing, and managing measures to prevent, mitigate, and respond to flooding in a specific region.
-
B.
canal authority
A canal authority is an organization responsible for managing, operating, and regulating a canal and its associated waterways, infrastructure, and traffic.
-
C.
watershed association
A watershed association is a community-based organization dedicated to protecting, restoring, and sustainably managing the land, water, and ecological resources within a specific watershed.
-
D.
fish and wildlife agency
A fish and wildlife agency is a governmental or tribal organization responsible for conserving, managing, and regulating fish, wildlife, and their habitats for ecological health and public benefit.
-
E.
natural resources management agency
chosen
A natural resources management agency is an organization responsible for planning, regulating, and overseeing the sustainable use, conservation, and restoration of natural resources such as land, water, forests, wildlife, and minerals.
- 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_69c008a45d008190832a9e19f5d63406 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:16 p.m.