Triple
T13689469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Political-Administrative Statute of the Autonomous Region of the Azores |
E328222
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional statute |
C27458
|
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: regional statute Context triple: [Political-Administrative Statute of the Autonomous Region of the Azores, instanceOf, regional statute]
-
A.
regional legislation
chosen
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.
-
B.
statute
A statute is a formal written law enacted by a legislative body that establishes rules, obligations, or prohibitions within a governing jurisdiction.
-
C.
internal statute
An internal statute is a formal, binding rule or regulation adopted within an organization to govern its internal operations, decision-making processes, and member conduct.
-
D.
subnational constitution
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.
-
E.
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.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:53 p.m.