Triple
T11159368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reference re Supreme Court Act, ss. 5 and 6 (2014) |
E263993
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | constitutional reference |
C29302
|
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 reference Context triple: [Reference re Supreme Court Act, ss. 5 and 6 (2014), instanceOf, constitutional reference]
-
A.
constitutional provision
A constitutional provision is a specific, authoritative rule or principle written into a constitution that defines the structure, powers, and limits of government and the rights of individuals.
-
B.
constitutional clause
A constitutional clause is a specific provision or section within a constitution that establishes, limits, or defines governmental powers, rights, or procedures.
-
C.
constitutional laws
Constitutional laws are the fundamental legal rules and principles that define a state's structure of government, distribute powers among its institutions, and protect the basic rights and freedoms of individuals.
-
D.
constitutional statute
A constitutional statute is a fundamental law enacted by a legislature that, while formally an ordinary statute, has quasi-constitutional status because it implements, structures, or protects core constitutional principles and cannot be amended or repealed without special procedures or heightened scrutiny.
-
E.
constitutional concept
A constitutional concept is an abstract legal and political idea that defines, structures, or constrains the organization, powers, and fundamental principles of a constitutional system.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:28 p.m.