Triple
T34830995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legislative framework of British Columbia |
E1004063
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | provincial legislative framework |
C45704
|
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 legislative framework Context triple: [Legislative framework of British Columbia, instanceOf, provincial legislative framework]
-
A.
provincial policy framework
A provincial policy framework is a structured set of guiding principles, objectives, and regulations developed at the provincial level to coordinate and direct public policies, programs, and resource allocation across sectors within that jurisdiction.
-
B.
regional legislation
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.
-
C.
Canadian provincial legislation
chosen
Canadian provincial legislation comprises the body of laws enacted by provincial and territorial legislatures that govern matters within their constitutional jurisdictions, such as education, healthcare, property, and civil rights.
-
D.
provincial authority
A provincial authority is a regional governing body responsible for administering laws, policies, and public services within a specific province under a broader national framework.
-
E.
legal-political framework
A legal-political framework is the structured system of laws, institutions, and governing principles that defines how power is distributed, exercised, and constrained within a society.
- 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_69f76db7d1b4819093bd4912d80d845d |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.