Triple
T9631342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quebec general election |
E232809
|
entity |
| Predicate | hasCampaignPeriod |
P53426
|
FINISHED |
| Object | official election campaign |
—
|
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: official election campaign | Statement: [Quebec general election, hasCampaignPeriod, official election campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampaignPeriod Context triple: [Quebec general election, hasCampaignPeriod, official election campaign]
-
A.
hasInaugurationPeriod
Indicates the time span during which an inauguration event takes place or is officially in effect.
-
B.
campaignEra
chosen
Indicates the historical or temporal period during which a particular campaign takes place or is active.
-
C.
hasMajorCampaign
Indicates that an entity is associated with or participates in a primary, large-scale campaign.
-
D.
hasCountingPeriod
Indicates that there is a defined time span or interval over which occurrences, quantities, or measurements related to an entity are counted or aggregated.
-
E.
hasAwardPeriod
Indicates the time span or date range during which an award is valid, active, or applicable.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b2621408190bfe2ea5a05359ee0 |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:11 p.m.