Triple
T7140135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish parliamentary reform of 1906 |
E166419
|
entity |
| Predicate | suffrageScope |
P44277
|
FINISHED |
| Object | men and women |
—
|
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: men and women | Statement: [Finnish parliamentary reform of 1906, suffrageScope, men and women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suffrageScope Context triple: [Finnish parliamentary reform of 1906, suffrageScope, men and women]
-
A.
suffrageIncludes
chosen
Indicates that the scope of a group’s voting rights or electoral franchise extends to and encompasses the specified category of people or entities.
-
B.
suffrage
Indicates that an entity has the right or privilege to vote in political or organizational decision-making processes.
-
C.
womenSuffrageGrantedIn
Indicates that women were granted the legal right to vote in a specified place or jurisdiction.
-
D.
excludedFromSuffrage
Indicates that certain individuals or groups are denied the right to vote in a political or electoral process.
-
E.
introducedSuffrageType
Indicates that an entity initiated or brought into effect a particular type or form of suffrage.
- 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_69c6888579d481909e05a8d6b81bf733 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7775e408190b880abde0a3f8d12 |
completed | March 27, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.