Triple
T34443310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calgary Stampeders–Edmonton Elks rivalry |
E884152
|
entity |
| Predicate | LabourDayClassicFrequency |
P179653
|
FINISHED |
| Object | annual |
—
|
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: annual | Statement: [Calgary Stampeders–Edmonton Elks rivalry, LabourDayClassicFrequency, annual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LabourDayClassicFrequency Context triple: [Calgary Stampeders–Edmonton Elks rivalry, LabourDayClassicFrequency, annual]
-
A.
LabourDayClassicHost
Indicates that the subject team serves as the host of the Labour Day Classic game against the specified opponent.
-
B.
hasWeeklyHolyDay
Indicates that an entity observes or is associated with a recurring holy or sacred day that occurs weekly.
-
C.
rankAmongHolidays
Indicates how a holiday is positioned or ordered in importance, popularity, or precedence relative to other holidays.
-
D.
LabourDayClassicVisitor
Indicates that an entity attends or has attended the Labour Day Classic event.
-
E.
holidaySchedule
Indicates the planned dates, times, and durations during which holidays occur or are observed.
- F. None of above. chosen
Provenance (4 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_69f7238172748190b8cd340ad1f4ba80 |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f72349f1108190b6a06758ab2f40bb |
completed | May 3, 2026, 10:28 a.m. |
Created at: May 1, 2026, 2 a.m.