Triple

T32804342
Position Surface form Disambiguated ID Type / Status
Subject New York Giants vs. Philadelphia Eagles game, December 2010 E838979 entity
Predicate decisivePlayTeam P41441 FINISHED
Object Philadelphia Eagles 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: Philadelphia Eagles | Statement: [New York Giants vs. Philadelphia Eagles game, December 2010, decisivePlayTeam, Philadelphia Eagles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: decisivePlayTeam
Context triple: [New York Giants vs. Philadelphia Eagles game, December 2010, decisivePlayTeam, Philadelphia Eagles]
  • A. decisivePlayPlayer
    Indicates that a player made a decisive play that significantly influenced the outcome of a game or match.
  • B. decisiveGameRoadTeam
    Indicates that the game was a decisive or series-clinching matchup in which the team playing on the road participated as the road team.
  • C. decidingScoreTeam chosen
    Indicates the team whose score ultimately determines the outcome or winner in a game or match.
  • D. decidingPlayOffenseTeam
    Indicates that an entity is choosing or determining which team will play on offense.
  • E. decidingPlay
    Indicates that an action or event serves as the critical play that determines the outcome of a game or contest.
  • 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_69f3493d35208190b4351b4e85f2fa16 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f70b966860819089cf92927f47c5f1 completed May 3, 2026, 8:47 a.m.
PD Predicate disambiguation batch_69f70abe43e08190b2a30930d96247c1 completed May 3, 2026, 8:43 a.m.
Created at: May 1, 2026, 1:15 a.m.