Triple
T32841513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 Constitution Order |
E839984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | constitutional order in council |
C61103
|
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 order in council Context triple: [2010 Constitution Order, instanceOf, constitutional order in council]
-
A.
legal order in council
chosen
A legal order in council is a formal directive issued by a sovereign or head of state, typically on the advice of the executive council or cabinet, that has the force of law without requiring full legislative approval.
-
B.
Constitutional order
A constitutional order is a structured system of governance in which political power is defined, limited, and organized by a foundational set of legal principles and institutions, typically embodied in a constitution.
-
C.
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.
-
D.
European Council decision
A European Council decision is a binding legal act adopted by the European Council that sets specific rules, measures, or positions for particular situations or addressees within the European Union’s institutional framework.
-
E.
constitutional convention system
A constitutional convention system is a structured process and institutional framework through which representatives are convened to draft, debate, and adopt a new constitution or major constitutional amendments for a political entity.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:16 a.m.