Triple
T24787519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statutes of Autonomy |
E620158
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sub‑state constitution |
C13681
|
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: sub‑state constitution Context triple: [Statutes of Autonomy, instanceOf, sub‑state constitution]
-
A.
subnational constitution
chosen
A subnational constitution is a fundamental legal document that organizes and governs a constituent unit within a federal or decentralized state—such as a province, state, or region—by defining its institutions, powers, and relationship to the national constitution.
-
B.
subnational legislature
A subnational legislature is a lawmaking body that operates below the national level—such as a state, provincial, or regional assembly—responsible for creating and overseeing laws and policies within its specific territorial jurisdiction.
-
C.
sub‑national government
A sub-national government is a governing authority below the national level—such as a state, province, region, or municipality—that exercises political, administrative, and often fiscal powers within a defined territorial jurisdiction.
-
D.
subordinate legislation
Subordinate legislation is law made by an authority other than the legislature (such as a minister or agency) under powers delegated by an Act of Parliament or primary legislation.
-
E.
state government
A state government is the political organization and administrative apparatus that exercises authority, creates and enforces laws, and provides public services within a specific subnational region of a country.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:46 a.m.