Triple
T28377439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitutional and parliamentary conventions of Canada |
E718790
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | constitutional convention system |
C53969
|
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: constitutional convention system Context triple: [Constitutional and parliamentary conventions of Canada, instanceOf, constitutional convention system]
-
A.
constitutional convention
A constitutional convention is a formal gathering of representatives convened to draft, revise, or replace a constitution or fundamental governing framework of a political entity.
-
B.
constitutional convention document
A constitutional convention document is the formal written record produced by a constitutional convention that outlines proposed or adopted foundational principles, governmental structures, and legal frameworks for a political entity.
-
C.
constitutional institution
A constitutional institution is a formally established body or office whose powers, functions, and structure are defined and limited by a constitution to uphold and operate the fundamental framework of a state.
-
D.
constitutional accord
A constitutional accord is a formal agreement among key political actors or jurisdictions that defines, revises, or clarifies the fundamental rules, powers, and structures of a constitutional system.
-
E.
constitutionalism
Constitutionalism is the principle that government authority is derived from and limited by a fundamental law or constitution, which protects individual rights and structures political power.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:04 a.m.