Triple

T36024837
Position Surface form Disambiguated ID Type / Status
Subject Michigan–Minnesota football rivalry E1042097 entity
Predicate homeStadiumForMinnesotaHomeGames P18826 FINISHED
Object Huntington Bank Stadium 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: Huntington Bank Stadium | Statement: [Michigan–Minnesota football rivalry, homeStadiumForMinnesotaHomeGames, Huntington Bank Stadium]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: homeStadiumForMinnesotaHomeGames
Context triple: [Michigan–Minnesota football rivalry, homeStadiumForMinnesotaHomeGames, Huntington Bank Stadium]
  • A. homeStadiumForGame
    Indicates that a particular stadium is the venue where a specific game is hosted as the home team's field.
  • B. homeStadiumTeam
    Indicates that a particular stadium serves as the designated home venue for a specific sports team.
  • C. playsHomeGamesOn chosen
    Indicates that an entity regularly hosts its home games or matches at a specified location or venue.
  • D. hasSportsTeamVenueFor
    Indicates that a venue serves as the home or hosting location for a particular sports team.
  • E. homeStadiumVariesByTeam
    Indicates that the specific home stadium associated with an event or game depends on which team is involved.
  • 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_69f76e2c568881909e1e21f85252b0f0 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7b69b333081909cadbed3fcb8ecf5 completed May 3, 2026, 8:56 p.m.
PD Predicate disambiguation batch_69f7b4c2a5f8819094ad4621d7b97e0c completed May 3, 2026, 8:49 p.m.
Created at: May 3, 2026, 4:07 p.m.