Triple
T1032985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legislative Assembly |
E22294
|
entity |
| Predicate | electionBasedOn |
P13521
|
FINISHED |
| Object | census 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: census suffrage | Statement: [Legislative Assembly, electionBasedOn, census suffrage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionBasedOn Context triple: [Legislative Assembly, electionBasedOn, census suffrage]
-
A.
electoralBasis
chosen
Indicates the principle, rule, or criterion by which representatives or officials are chosen in an election.
-
B.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
-
C.
electionMethod
Indicates the process or system used to select a candidate or make a decision in an election.
-
D.
electoralBase
Indicates the group of voters or supporters that primarily backs or sustains a particular candidate, party, or political movement in elections.
-
E.
electedFrom
Indicates that an individual has been chosen through an election to represent or serve a specific geographic area, constituency, or jurisdiction.
- 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8d669448190955507e2e4975b9f |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b728ad3481909cf1430349cb9bba |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.