Triple

T33941546
Position Surface form Disambiguated ID Type / Status
Subject Memorial Day Miracle E870178 entity
Predicate hasOpponentFranchise P86168 FINISHED
Object Portland Trail Blazers 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: Portland Trail Blazers | Statement: [Memorial Day Miracle, hasOpponentFranchise, Portland Trail Blazers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOpponentFranchise
Context triple: [Memorial Day Miracle, hasOpponentFranchise, Portland Trail Blazers]
  • A. hasOpposingTeamsLedBy
    Indicates a relationship where a competitive event or context features two opposing teams, each directed or managed by a specific leader.
  • B. wasOpponentOf chosen
    Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
  • C. playsForFranchise
    Indicates that one entity is an athlete or performer who is a member of, or competes on behalf of, a particular sports franchise or team.
  • D. hasRivalryIn
    Indicates that two entities are in a state of competition or opposition within a specific domain, context, or field.
  • E. hasHomeStadiumInRivalry
    Indicates that one entity’s home stadium is the venue used when it participates in a rivalry with another entity.
  • 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_69f3499b0dd48190b07b4b60babcee02 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fba78aca4c8190b8f1831e8cc04e06 completed May 6, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69fba34a65a4819088bac6c17542d71c completed May 6, 2026, 8:23 p.m.
Created at: May 1, 2026, 1:49 a.m.