Triple
T26739765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canton of Appenzell Innerrhoden |
E674213
|
entity |
| Predicate | hasVotingRightsInCouncilOfStates |
P78466
|
FINISHED |
| Object | one seat |
—
|
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: one seat | Statement: [Canton of Appenzell Innerrhoden, hasVotingRightsInCouncilOfStates, one seat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVotingRightsInCouncilOfStates Context triple: [Canton of Appenzell Innerrhoden, hasVotingRightsInCouncilOfStates, one seat]
-
A.
hasVotingRightsInHouse
Indicates that an entity possesses the legal authority to vote in the decision-making processes of a specified house or legislative body.
-
B.
hasElectoralRight
Indicates that an entity possesses the legal right to participate in elections, typically by voting or standing as a candidate.
-
C.
mayHaveCastingVote
Indicates that an entity is permitted to exercise a casting (tie-breaking) vote in a decision-making process.
-
D.
hasVotingRightInSenate
chosen
Indicates that an entity possesses the legal right to participate in voting within a senate body.
-
E.
hasCouncilSeat
Indicates that an entity holds a position or seat on a governing council.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 3:48 a.m.