Triple
T15493995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Constitution of 1848 |
E378766
|
entity |
| Predicate | limitedCantonalSovereignty |
P14912
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [Federal Constitution of 1848, limitedCantonalSovereignty, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedCantonalSovereignty Context triple: [Federal Constitution of 1848, limitedCantonalSovereignty, true]
-
A.
hasAutonomousCanton
Indicates that an entity possesses or is associated with a canton that has autonomous or self-governing status.
-
B.
foundingCantons
Indicates that the referenced entities are the original member regions or states that established or founded a larger political or organizational unit.
-
C.
reducedSovereigntyOf
chosen
Indicates that one entity has diminished, constrained, or otherwise limited the sovereignty or autonomous decision-making power of another entity.
-
D.
numberOfCantons
Indicates the total count of cantons associated with or contained within a given entity.
-
E.
sovereigntyStatus
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
- F. None of above.
Provenance (3 batches)
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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fad723481908d2aa33e8f065f2f |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:49 a.m.