Triple
T7078740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of the Republic and Canton of Geneva |
E164889
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cantonal 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: cantonal constitution Context triple: [Constitution of the Republic and Canton of Geneva, instanceOf, cantonal 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.
Swiss federal law
Swiss federal law is the body of legal rules and principles enacted or recognized at the national level in Switzerland that uniformly govern matters within the competence of the Swiss Confederation across all cantons.
-
D.
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.
-
E.
Swiss canton
A Swiss canton is a semi-sovereign federal state within Switzerland, possessing its own constitution, government, and legislative authority under the Swiss federal 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_69c6887cbc6c8190bdfac42d940f4d8a |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:40 p.m.