Triple
T2692258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rob Ford |
E58428
|
entity |
| Predicate | unsuccessfulCandidacy |
P12344
|
FINISHED |
| Object | 2014 Toronto mayoral election |
—
|
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: 2014 Toronto mayoral election | Statement: [Rob Ford, unsuccessfulCandidacy, 2014 Toronto mayoral election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unsuccessfulCandidacy Context triple: [Rob Ford, unsuccessfulCandidacy, 2014 Toronto mayoral election]
-
A.
losingRunningMate
Indicates that one entity is the running mate who was on the losing side in an electoral contest involving another entity.
-
B.
defeatedCandidate
Indicates that one candidate has won an election or contest against another candidate, causing the other to lose.
-
C.
popularVoteLoser
Indicates that the subject became the winner of an election despite receiving fewer popular votes than at least one opponent.
-
D.
wasCandidateIn
chosen
Indicates that an entity served as a candidate in a particular election, contest, or selection process.
-
E.
announcedCandidacyFor
Indicates that an entity has publicly declared their intention to run as a candidate for a specific position, office, or role.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda0dd97c81909a60cf200f57c087 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81ea5d88190ab5c8f8b8064b931 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.