Triple
T10764879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFL Labour Day Classic |
E253927
|
entity |
| Predicate | hasMatchup |
P42689
|
FINISHED |
| Object | Hamilton Tiger-Cats vs Toronto Argonauts |
—
|
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: Hamilton Tiger-Cats vs Toronto Argonauts | Statement: [CFL Labour Day Classic, hasMatchup, Hamilton Tiger-Cats vs Toronto Argonauts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMatchup Context triple: [CFL Labour Day Classic, hasMatchup, Hamilton Tiger-Cats vs Toronto Argonauts]
-
A.
matchOf
chosen
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
B.
definingMatchup
Indicates a matchup that is especially significant or decisive in defining the outcome, narrative, or importance of a broader event or competition.
-
C.
hasChampionshipMatch
Indicates that an entity is associated with a specific championship-level match, typically as an organizer, participant, or host.
-
D.
conferenceMatchupType
Indicates the type or category of matchup between entities within a conference context (e.g., intra-conference vs. inter-conference).
-
E.
matchupFrequency
Indicates how often a particular pair or set of entities are matched or paired against each other within a given context or timeframe.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d731a5d5248190badfc5a8ab0215d6 |
completed | April 9, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.