Triple

T2483113
Position Surface form Disambiguated ID Type / Status
Subject Arizona Coyotes E55863 entity
Predicate NHLExpansionRelocationStatus P40302 FINISHED
Object relocated franchise 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: relocated franchise | Statement: [Arizona Coyotes, NHLExpansionRelocationStatus, relocated franchise]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: NHLExpansionRelocationStatus
Context triple: [Arizona Coyotes, NHLExpansionRelocationStatus, relocated franchise]
  • A. NHLaffiliate
    Indicates that one entity serves as a National Hockey League (NHL) affiliate or farm team relationship to another, typically linking a minor-league team to its parent NHL club.
  • B. NHLExpansionTeam
    Indicates that a team is an officially recognized expansion franchise added to the NHL beyond its original set of teams.
  • C. joinedNHL
    Indicates that an entity became a member of, or started playing in, the National Hockey League (NHL).
  • D. NHLParentFranchiseLocation
    Indicates the geographic location associated with the parent franchise of an NHL team.
  • E. NHLparentClub
    Indicates that one hockey team serves as the parent or primary affiliate organization for another team within the NHL system.
  • 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_69ab49e670a88190b928e08302381710 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abd20b6d008190acec0eb172e218c9 completed March 7, 2026, 7:21 a.m.
PD Predicate disambiguation batch_69abd0b7cf088190bcff4dac6150044c completed March 7, 2026, 7:16 a.m.
PDg Predicate description generation batch_69abd209d934819093600889af9104c3 completed March 7, 2026, 7:21 a.m.
Created at: March 6, 2026, 9:45 p.m.