Triple
T27298028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of States of the Swiss Confederation of 1848 |
E688821
|
entity |
| Predicate | numberOfSeatsPerFullCanton |
P76381
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Council of States of the Swiss Confederation of 1848, numberOfSeatsPerFullCanton, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSeatsPerFullCanton Context triple: [Council of States of the Swiss Confederation of 1848, numberOfSeatsPerFullCanton, 2]
-
A.
minimumSeatsPerCanton
Indicates the minimum number of seats that must be allocated to each canton in a representative body or distribution scheme.
-
B.
numberOfCantons
Indicates the total count of cantons associated with or contained within a given entity.
-
C.
regionSeatsCount
chosen
Indicates the number of seats allocated or available within a specific region.
-
D.
populationRankInCanton
Indicates the relative position of an entity in terms of population size compared to other entities within the same canton.
-
E.
maximumSeatsPerState
Indicates the upper limit on the number of seats that any single state is allowed to have.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: April 27, 2026, 11:20 a.m.