Triple
T1182518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 23 of the Constitution of Norway |
E25169
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | article of the Constitution of Norway |
C569
|
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: article of the Constitution of Norway Context triple: [Article 23 of the Constitution of Norway, instanceOf, article of the Constitution of Norway]
-
A.
constitutional provision
chosen
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.
clause of the United States Constitution
A clause of the United States Constitution is a distinct, self-contained provision within the document that establishes specific powers, rights, limitations, or procedures governing the federal government and its relationship to the states and the people.
-
C.
written constitution
A written constitution is a formal, codified document that outlines the fundamental principles, structures, powers, and limits of a government, as well as the rights and duties of its citizens.
-
D.
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.
-
E.
constitutional instrument
A constitutional instrument is a formal legal document or set of provisions that establishes, organizes, or amends the fundamental principles and structures of a state or governing 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:45 p.m.