Triple
T16187950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The City of Winnipeg Charter |
E392858
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governing legislation |
C27458
|
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: governing legislation Context triple: [The City of Winnipeg Charter, instanceOf, governing legislation]
-
A.
canonical legislation
Canonical legislation is the body of laws and regulations established by ecclesiastical authority to govern the doctrine, discipline, and administration of a religious institution, particularly within the Christian tradition.
-
B.
security legislation
Security legislation comprises the laws and regulations designed to protect a nation’s security interests by governing activities such as surveillance, data protection, counterterrorism, and the use of security forces.
-
C.
regional legislation
chosen
Regional legislation comprises the laws, regulations, and legal frameworks enacted by subnational authorities (such as states, provinces, or regions) to govern matters within their territorial jurisdiction.
-
D.
financial legislation
Financial legislation comprises the laws and regulations that govern the creation, management, oversight, and stability of financial systems, markets, institutions, and transactions.
-
E.
public finance legislation
Public finance legislation comprises the body of laws and regulations that govern how governments raise revenue, allocate expenditures, manage public debt, and oversee fiscal responsibility to achieve economic and social policy objectives.
- 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.