Triple
T4289012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Section 1 of Article III of the United States Constitution |
E97340
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | constitutional section |
C567
|
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 section Context triple: [Section 1 of Article III of the United States Constitution, instanceOf, constitutional section]
-
A.
constitutional provision
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.
constitutional clause
chosen
A constitutional clause is a specific provision or section within a constitution that establishes, limits, or defines governmental powers, rights, or procedures.
-
C.
constitutional statute
A constitutional statute is a fundamental law enacted by a legislature that, while formally an ordinary statute, has quasi-constitutional status because it implements, structures, or protects core constitutional principles and cannot be amended or repealed without special procedures or heightened scrutiny.
-
D.
constitutional concept
A constitutional concept is an abstract legal and political idea that defines, structures, or constrains the organization, powers, and fundamental principles of a constitutional system.
-
E.
constitutional laws
Constitutional laws are the fundamental legal rules and principles that define a state's structure of government, distribute powers among its institutions, and protect the basic rights and freedoms of individuals.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:08 p.m.