Triple
T7831625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charter of the City of St. Louis |
E181582
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local constitution |
C13681
|
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: local constitution Context triple: [Charter of the City of St. Louis, instanceOf, local constitution]
-
A.
subnational constitution
chosen
A subnational constitution is a fundamental legal document that organizes and governs a constituent unit within a federal or decentralized state—such as a province, state, or region—by defining its institutions, powers, and relationship to the national constitution.
-
B.
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.
-
C.
constitutional convention document
A constitutional convention document is the formal written record produced by a constitutional convention that outlines proposed or adopted foundational principles, governmental structures, and legal frameworks for a political entity.
-
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.
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_69ca8284a25c8190a1a20afad30da792 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:44 p.m.