Triple
T16187993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winnipeg Fire Paramedic Service (policy and budget) |
E392859
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public sector budgeting framework |
C28509
|
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: public sector budgeting framework Context triple: [Winnipeg Fire Paramedic Service (policy and budget), instanceOf, public sector budgeting framework]
-
A.
budgetary framework
chosen
A budgetary framework is a structured system of rules, processes, and assumptions that guides how financial resources are planned, allocated, monitored, and controlled over a specific period.
-
B.
budgetary planning exercise
A budgetary planning exercise is a structured activity in which individuals or organizations forecast income and expenses over a specific period to allocate resources, evaluate trade-offs, and ensure financial goals are achievable.
-
C.
public sector investment schedule
A public sector investment schedule is a planned timeline and allocation of government capital expenditures across projects and sectors to achieve specified policy, economic, and social objectives.
-
D.
government budget
A government budget is a financial plan that outlines a government's projected revenues and expenditures over a specific period, typically one fiscal year, to achieve its economic and policy objectives.
-
E.
federal government framework
A federal government framework is a structural system that defines how power, responsibilities, and relationships are distributed and coordinated between a central authority and its constituent regional or state governments.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:02 a.m.