Triple
T37261563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statute of the Region of Apulia |
E924270
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | constitutional law of a region of Italy |
C3453
|
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 law of a region of Italy Context triple: [Statute of the Region of Apulia, instanceOf, constitutional law of a region of Italy]
-
A.
organo giurisdizionale italiano
Un organo giurisdizionale italiano è un’istituzione pubblica prevista dall’ordinamento che esercita la funzione giurisdizionale, applicando il diritto per risolvere controversie e garantire la tutela dei diritti e degli interessi legittimi.
-
B.
Italian law
Italian law is the legal system of Italy, rooted in Roman law and codified civil law traditions, governing public, private, and criminal matters through a hierarchy of constitutional, statutory, and regulatory norms.
-
C.
constitutional law case
A constitutional law case is a legal dispute that requires a court to interpret and apply a nation's constitution to determine the validity of government actions, laws, or policies.
-
D.
constitutional law topic
A constitutional law topic is a specific subject area concerning the interpretation, application, or structure of a nation's constitution, including the distribution of governmental powers and the protection of individual rights.
-
E.
constitutional law
chosen
Constitutional law is the body of legal principles and rules that defines the structure, powers, and limits of government and protects fundamental rights under a nation's constitution.
- 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.