Triple
T24906703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1993 Canadian federal election |
E623727
|
entity |
| Predicate | totalRejectedBallots |
P157790
|
FINISHED |
| Object | 85,989 |
—
|
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: 85,989 | Statement: [1993 Canadian federal election, totalRejectedBallots, 85,989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalRejectedBallots Context triple: [1993 Canadian federal election, totalRejectedBallots, 85,989]
-
A.
numberOfBallots
Indicates the total count of ballots associated with a particular election, contest, or voting event.
-
B.
ballotsCountedBy
Indicates that the ballots in an election or vote are counted or tallied by a specified person, group, or entity.
-
C.
totalVotesCast
Indicates the total number of votes that have been cast in a given election or voting event.
-
D.
totalValidVotes
Indicates the total number of votes in an election or decision process that are considered valid according to the defined rules.
-
E.
votersCouldRejectList
Indicates that voters have the option or authority to reject a proposed list (such as a candidate list or item list) rather than accept or select from it.
- F. None of above. chosen
Provenance (4 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 5:27 a.m.