Triple
T34515836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saskatchewan Roughriders–Winnipeg Blue Bombers rivalry |
E886148
|
entity |
| Predicate | hasHomeCityForOtherTeam |
P127320
|
FINISHED |
| Object | Winnipeg |
—
|
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: Winnipeg | Statement: [Saskatchewan Roughriders–Winnipeg Blue Bombers rivalry, hasHomeCityForOtherTeam, Winnipeg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeCityForOtherTeam Context triple: [Saskatchewan Roughriders–Winnipeg Blue Bombers rivalry, hasHomeCityForOtherTeam, Winnipeg]
-
A.
hasHomeCity
Indicates that an entity’s primary or official city of residence or affiliation is a specified city.
-
B.
homeCityTeamOf
Indicates that one entity is the sports team based in and representing the home city of the other entity.
-
C.
homeCityOfRivalTeam
chosen
Indicates the city that serves as the home base for a team’s rival.
-
D.
hasHomeCityStadium
Indicates that a sports team or organization has its primary home stadium located in a specific city.
-
E.
hasHomeCityTeamStadium
Indicates that a sports team’s home city is associated with a specific stadium where the team primarily hosts its home games.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 1, 2026, 2:01 a.m.