Triple
T34443311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calgary Stampeders–Edmonton Elks rivalry |
E884152
|
entity |
| Predicate | LabourDayClassicTiming |
P75770
|
FINISHED |
| Object | Labour Day weekend |
—
|
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: Labour Day weekend | Statement: [Calgary Stampeders–Edmonton Elks rivalry, LabourDayClassicTiming, Labour Day weekend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LabourDayClassicTiming Context triple: [Calgary Stampeders–Edmonton Elks rivalry, LabourDayClassicTiming, Labour Day weekend]
-
A.
LabourDayClassicHost
Indicates that the subject team serves as the host of the Labour Day Classic game against the specified opponent.
-
B.
LabourDayClassicFrequency
Indicates how often the Labour Day Classic event occurs within a given time period.
-
C.
LabourDayClassicVisitor
Indicates that an entity attends or has attended the Labour Day Classic event.
-
D.
timeOfCelebration
chosen
Indicates the specific time or period during which a celebration takes place.
-
E.
approximateTimeOfDayOfEventCommemorated
Indicates the general time of day during which the commemorated event is understood to have occurred.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2 a.m.