Triple
T37469837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overwatch World Cup 2019 |
E931125
|
entity |
| Predicate | MVPInGameName |
P187794
|
FINISHED |
| Object | Corey |
—
|
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: Corey | Statement: [Overwatch World Cup 2019, MVPInGameName, Corey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MVPInGameName Context triple: [Overwatch World Cup 2019, MVPInGameName, Corey]
-
A.
MVPtrophyName
Indicates the name or title assigned to a specific MVP (Most Valuable Player) trophy.
-
B.
MVP
Indicates that an entity has been selected or recognized as the “Most Valuable Player,” i.e., the most outstanding or impactful participant within a specific game, season, event, or context.
-
C.
MVPInLeague
Indicates that an entity was selected as the Most Valuable Player (MVP) within a particular league for a given season or time period.
-
D.
MVPposition
Indicates the position or role in which an entity served when it was recognized as the Most Valuable Player (MVP).
-
E.
finalsMVPInGameName
Indicates that a player was named the Most Valuable Player (MVP) in a specific finals game identified by its name.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8e61d5a48190afc273af1fb54af9 |
completed | May 6, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0c53c08190b64291bac58cdb4c |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb8dfe70d08190b2558cdfcc1b15c0 |
completed | May 6, 2026, 6:52 p.m. |
Created at: May 3, 2026, 4:17 p.m.