Triple
T8163725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Alliance |
E190636
|
entity |
| Predicate | officialOppositionPeriodStart |
P15443
|
FINISHED |
| Object | 2000-11-27 |
—
|
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: 2000-11-27 | Statement: [Canadian Alliance, officialOppositionPeriodStart, 2000-11-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialOppositionPeriodStart Context triple: [Canadian Alliance, officialOppositionPeriodStart, 2000-11-27]
-
A.
oppositionPeriodStart
chosen
Indicates the point in time when a formal opposition or challenge against something begins.
-
B.
startTime (as Leader of the Opposition)
Indicates the date and time when an individual began serving in the role of Leader of the Opposition.
-
C.
termEndAsLeaderOfOpposition
Indicates the point in time when an entity’s tenure serving as leader of the opposition comes to an end.
-
D.
lastOfficeHolderStartDate
Indicates the date on which the most recent person to hold a particular office or position began their term.
-
E.
formerMPStartYear
Indicates the year in which an individual began their period of service as a former Member of Parliament (i.e., the start year of their tenure as an MP).
- 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_69ca82c0ef14819083713f4473dd847c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4557ebc88190b4e2cab258374d23 |
completed | March 31, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:38 p.m.