Triple
T26934221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1979 Canadian federal election |
E678323
|
entity |
| Predicate | progressiveConservativeSeatsWon |
P20303
|
FINISHED |
| Object | 136 |
—
|
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: 136 | Statement: [1979 Canadian federal election, progressiveConservativeSeatsWon, 136]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: progressiveConservativeSeatsWon Context triple: [1979 Canadian federal election, progressiveConservativeSeatsWon, 136]
-
A.
ConservativeSeatsWon
chosen
Indicates the number of parliamentary or legislative seats won by the Conservative party in an election.
-
B.
numberOfVotesConservative
Indicates the number of votes that were cast for the Conservative option or party in a given context.
-
C.
oppositionPartySeatsWon
Indicates the number of legislative seats secured by the opposition party in an election or governing body.
-
D.
ConservativeSeatChange
Indicates the change in the number of seats held by the Conservative party between two electoral periods.
-
E.
LabourSeatsWon
Indicates the number of parliamentary seats won by the Labour Party 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 6:14 a.m.