Triple
T37039432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 Overwatch League season |
E916738
|
entity |
| Predicate | grandFinalMVP |
P131267
|
FINISHED |
| Object | Lee "LIP" Jae-won |
—
|
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: Lee "LIP" Jae-won | Statement: [2021 Overwatch League season, grandFinalMVP, Lee "LIP" Jae-won]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grandFinalMVP Context triple: [2021 Overwatch League season, grandFinalMVP, Lee "LIP" Jae-won]
-
A.
grandFinalsMVPInGameName
Indicates the in-game name of the player who was awarded MVP in the grand finals match.
-
B.
finalsMVPFor
chosen
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.
worldChampionshipMVP
Indicates that an entity was selected as the Most Valuable Player (MVP) of a world championship event.
-
D.
mostValuablePlayerAward
Indicates that an entity has received a "Most Valuable Player" award recognizing it as the most outstanding performer in a particular context or competition.
-
E.
FinalsMVPSeason
Indicates the season in which a player was awarded the Finals Most Valuable Player (MVP) honor.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:14 p.m.