Triple
T34574815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto Argonauts–Hamilton Tiger-Cats rivalry |
E887720
|
entity |
| Predicate | formerVenueTeam1 |
P54413
|
FINISHED |
| Object | Exhibition Stadium |
—
|
NE NERFINISHED |
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: Exhibition Stadium | Statement: [Toronto Argonauts–Hamilton Tiger-Cats rivalry, formerVenueTeam1, Exhibition Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerVenueTeam1 Context triple: [Toronto Argonauts–Hamilton Tiger-Cats rivalry, formerVenueTeam1, Exhibition Stadium]
-
A.
formerVenueTeam2Home
chosen
Indicates that the specified location was previously the home venue for the second team.
-
B.
primaryVenueTeam2
Indicates that the second team is the main or designated home team for a particular venue.
-
C.
formerTeam2Name
Indicates that an entity was previously associated with a second former team identified by this name.
-
D.
homeTeamForVenue
Indicates that a team is designated as the primary (home) team associated with a particular venue.
-
E.
institutionalAffiliationTeam1
Indicates that an entity is formally affiliated with or belongs to the first team of an institution.
- 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0010e46d948190a51111b5270fade7 |
completed | May 10, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_6a001061d34c8190bfe73f3d7c061eb7 |
completed | May 10, 2026, 4:58 a.m. |
Created at: May 1, 2026, 2:03 a.m.