Triple
T36648963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enumerated Powers Clause |
E904786
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | clause related to separation of powers |
C570
|
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: clause related to separation of powers Context triple: [Enumerated Powers Clause, instanceOf, clause related to separation of powers]
-
A.
constitutional clause
A constitutional clause is a specific provision or section within a constitution that establishes, limits, or defines governmental powers, rights, or procedures.
-
B.
clause of the United States Constitution
chosen
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.
constitutional accord
A constitutional accord is a formal agreement among key political actors or jurisdictions that defines, revises, or clarifies the fundamental rules, powers, and structures of a constitutional system.
-
D.
branch of government
A branch of government is a major division of a state's governing system, such as the executive, legislative, or judicial branch, each with distinct powers and responsibilities designed to balance and limit authority.
-
E.
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.
- 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_69f76e6d3a3c81909db73eda9e0516bd |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.