Triple

T11479780
Position Surface form Disambiguated ID Type / Status
Subject Montreal Canadiens–Boston Bruins rivalry E272112 entity
Predicate relativeImportanceToTeam2 P99518 FINISHED
Object one of Boston Bruins’ primary rivalries 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: one of Boston Bruins’ primary rivalries | Statement: [Montreal Canadiens–Boston Bruins rivalry, relativeImportanceToTeam2, one of Boston Bruins’ primary rivalries]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relativeImportanceToTeam2
Context triple: [Montreal Canadiens–Boston Bruins rivalry, relativeImportanceToTeam2, one of Boston Bruins’ primary rivalries]
  • A. relatedTeam
    Indicates that two teams are connected or associated with each other in a relevant or meaningful way.
  • B. associatedTeam
    Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
  • C. teamStrength
    Indicates the comparative overall capability or power level of a team, often used to assess how strong one team is relative to others.
  • D. teamScoring
    Indicates that a team achieves a score or points in a game, match, or competitive event.
  • E. decidingScoreTeam
    Indicates the team whose score ultimately determines the outcome or winner in a game or match.
  • F. None of above. chosen

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_69d6aae0c8d881908a5a360c0be3242e completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8294f0e948190b2e106beb86e4b2c completed April 9, 2026, 10:33 p.m.
PD Predicate disambiguation batch_69d8086ecd6c81908f424864857762d6 completed April 9, 2026, 8:13 p.m.
PDg Predicate description generation batch_69d8279925e4819089210611c0d8e61a completed April 9, 2026, 10:26 p.m.
Created at: April 8, 2026, 9:36 p.m.