Triple
T762077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article III, Section 1 of the United States Constitution |
E16092
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of the United States Constitution |
C2873
|
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: section of the United States Constitution Context triple: [Article III, Section 1 of the United States Constitution, instanceOf, section of the United States Constitution]
-
A.
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.
-
B.
amendment to the United States Constitution
An amendment to the United States Constitution is a formally adopted change or addition to the Constitution’s text that alters, clarifies, or expands the nation’s fundamental legal framework.
-
C.
constitutional clause
A constitutional clause is a specific provision or section within a constitution that establishes, limits, or defines governmental powers, rights, or procedures.
-
D.
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.
-
E.
section of a legal document
chosen
A section of a legal document is a distinct, numbered subdivision that organizes related provisions, rights, and obligations under a specific heading within the overall legal text.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.