Triple
T34537786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rider Nation |
E886716
|
entity |
| Predicate | hasRivalryWithFanBase |
P53223
|
FINISHED |
| Object | Winnipeg Blue Bombers fans |
—
|
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: Winnipeg Blue Bombers fans | Statement: [Rider Nation, hasRivalryWithFanBase, Winnipeg Blue Bombers fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalryWithFanBase Context triple: [Rider Nation, hasRivalryWithFanBase, Winnipeg Blue Bombers fans]
-
A.
hasFanBaseRivalry
chosen
Indicates a competitive or antagonistic relationship between the fan bases of two entities.
-
B.
hasRivalryIn
Indicates that two entities are in a state of competition or opposition within a specific domain, context, or field.
-
C.
hasRivalryRoot
Indicates that a rivalry relationship originates from, or is fundamentally based on, a particular source, cause, or underlying factor.
-
D.
hasRivalryEmotion
Indicates that one entity feels rivalry-based emotions, such as competitive tension or antagonistic comparison, toward another entity.
-
E.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 1, 2026, 2:02 a.m.