Triple
T1173997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Election Law of 1925 |
E24974
|
entity |
| Predicate | previousElectorateBasis |
P13521
|
FINISHED |
| Object | property-based suffrage |
—
|
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: property-based suffrage | Statement: [General Election Law of 1925, previousElectorateBasis, property-based suffrage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousElectorateBasis Context triple: [General Election Law of 1925, previousElectorateBasis, property-based suffrage]
-
A.
electoralBasis
chosen
Indicates the principle, rule, or criterion by which representatives or officials are chosen in an election.
-
B.
electoralBase
Indicates the group of voters or supporters that primarily backs or sustains a particular candidate, party, or political movement in elections.
-
C.
electoralHistory
Indicates the historical record of elections or voting outcomes associated with an entity.
-
D.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
E.
hasElectorate
Indicates that a political representative, office, or governing body is associated with and serves a specific group of voters or electoral district.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd53e4b48190abb2167f8074a6bc |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5844348190b01ac6506906ba3b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.