Triple

T36945860
Position Surface form Disambiguated ID Type / Status
Subject 2019 Overwatch League season E913908 entity
Predicate grandFinalsMVPInGameName P188928 FINISHED
Object Choihyobin 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: Choihyobin | Statement: [2019 Overwatch League season, grandFinalsMVPInGameName, Choihyobin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: grandFinalsMVPInGameName
Context triple: [2019 Overwatch League season, grandFinalsMVPInGameName, Choihyobin]
  • A. finalsMVPInGameName
    Indicates that a player was named the Most Valuable Player (MVP) in a specific finals game identified by its name.
  • B. finalsMVPFor
    Indicates that one entity is the Most Valuable Player (MVP) specifically for the finals of a competition, series, or tournament associated with another entity.
  • C. NBAFinalsMVP
    Indicates that the person was awarded the Most Valuable Player (MVP) honor for their performance in an NBA Finals series.
  • D. finalsMVPWinnerFromTeam
    Indicates that the specified player won the Finals MVP award while playing for the specified team.
  • E. ABAPlayoffsMVP
    Indicates that the subject was selected as the Most Valuable Player of the American Basketball Association (ABA) playoffs.
  • 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_69f76e8a6a5c81909c1febf32bf3fe23 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fbaf18085481908c774e8f8bbb9a41 completed May 6, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69fbadf1e6008190a71bbd196ba06844 completed May 6, 2026, 9:09 p.m.
PDg Predicate description generation batch_69fbaebbb7f88190b4edfd9b83550aad completed May 6, 2026, 9:12 p.m.
Created at: May 3, 2026, 4:13 p.m.