Triple
T27712132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1962 Canadian federal election |
E698717
|
entity |
| Predicate | leader2PopularVote |
P118893
|
FINISHED |
| Object | 2620200 |
—
|
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: 2620200 | Statement: [1962 Canadian federal election, leader2PopularVote, 2620200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leader2PopularVote Context triple: [1962 Canadian federal election, leader2PopularVote, 2620200]
-
A.
popularVoteRunnerUpVotes
chosen
Indicates the number of votes received by the candidate who finished second in the popular vote of an election.
-
B.
popularVoteWinner
Indicates that the subject is the candidate who received the highest number of individual votes cast by the electorate in an election.
-
C.
LabourPopularVote
Indicates the proportion of total votes cast in an election that were received by the Labour Party.
-
D.
popularVoteType
Indicates the specific method or category by which a popular vote is conducted or classified in an election or decision process.
-
E.
popularVote
Indicates the number or share of votes directly cast by the general electorate for a candidate or option in an election.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 3:02 p.m.