Triple
T22000291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vision Montréal |
E543305
|
entity |
| Predicate | contestedElectionLevel |
P8400
|
FINISHED |
| Object | mayoral elections in Montreal |
—
|
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: mayoral elections in Montreal | Statement: [Vision Montréal, contestedElectionLevel, mayoral elections in Montreal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestedElectionLevel Context triple: [Vision Montréal, contestedElectionLevel, mayoral elections in Montreal]
-
A.
hasOfficeContested
Indicates that an individual has been a candidate for a particular public office in an election.
-
B.
controlContested
Indicates that authority or dominance over something is disputed or challenged between two or more parties.
-
C.
resultContested
Indicates that the outcome or result of an event, process, or decision is being challenged or disputed by one or more parties.
-
D.
capitalContested
Indicates that the status of being the capital of a region or country is disputed or claimed by multiple parties.
-
E.
wasContestedIn
chosen
Indicates that an event, position, or decision was the subject of competition, dispute, or challenge within a particular context or proceeding.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127699a7881908a80b6e9e33fcc0b |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:20 p.m.