Triple
T16187992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winnipeg Fire Paramedic Service (policy and budget) |
E392859
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal policy framework |
C37106
|
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 policy framework Context triple: [Winnipeg Fire Paramedic Service (policy and budget), instanceOf, municipal policy framework]
-
A.
local and regional planning framework
A local and regional planning framework is a structured set of policies, processes, and tools that guide coordinated land use, infrastructure, and development decisions across municipalities and regions to achieve sustainable, equitable, and efficient growth.
-
B.
municipal administration
Municipal administration is the organizational structure and processes through which a local government manages public services, implements policies, and oversees the day-to-day operations of a municipality.
-
C.
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.
-
D.
municipal organization
A municipal organization is a local government entity responsible for providing public services, managing community resources, and implementing policies within a city, town, or other local jurisdiction.
-
E.
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.
- F. None of above. chosen
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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:02 a.m.