Triple

T34443326
Position Surface form Disambiguated ID Type / Status
Subject Calgary Stampeders–Edmonton Elks rivalry E884152 entity
Predicate relatedRivalryCategory P146762 FINISHED
Object Battle of Alberta sports rivalries E884152 NE 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: Battle of Alberta sports rivalries | Statement: [Calgary Stampeders–Edmonton Elks rivalry, relatedRivalryCategory, Battle of Alberta sports rivalries]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relatedRivalryCategory
Context triple: [Calgary Stampeders–Edmonton Elks rivalry, relatedRivalryCategory, Battle of Alberta sports rivalries]
  • A. associatedRivalry
    Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
  • B. rivalryBasis
    Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
  • C. hasRivalryCategory chosen
    Indicates that there exists a competitive or adversarial relationship between entities that falls into a specific classified type or category of rivalry.
  • D. isPartOfRivalry
    Indicates that one entity participates as a member or component in an ongoing rivalry involving another entity.
  • E. divisionRivalry
    Indicates a competitive or adversarial relationship between entities that belong to the same division or subgroup within a larger organization or system.
  • F. None of above.

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_6a037c8ae0248190b7e2ce4bf852c22d completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37183d20ac8190b5b163c73ea7ba67 completed June 20, 2026, 10:46 p.m.
PD Predicate disambiguation batch_6a0379fbe4a08190bfe65ebd141164e9 completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 2 a.m.