Triple
T36945862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Overwatch League season |
E913908
|
entity |
| Predicate | seasonMVPInGameName |
P194586
|
FINISHED |
| Object | sinatraa |
—
|
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: sinatraa | Statement: [2019 Overwatch League season, seasonMVPInGameName, sinatraa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonMVPInGameName Context triple: [2019 Overwatch League season, seasonMVPInGameName, sinatraa]
-
A.
finalsMVPInGameName
Indicates that a player was named the Most Valuable Player (MVP) in a specific finals game identified by its name.
-
B.
ABASeasonMVP
Indicates that an entity was selected as the Most Valuable Player for a particular season in the American Basketball Association (ABA).
-
C.
grandFinalsMVPInGameName
Indicates the in-game name of the player who was awarded MVP in the grand finals match.
-
D.
regularSeasonAward
Indicates that an entity received or is associated with an award specifically given for performance during the regular season of a competition or league.
-
E.
MVPPerformance
Indicates that an entity delivered a standout, most valuable player–level performance in a given context or event.
- 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_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69fd7b042a548190b3abe31bc3258278 |
completed | May 8, 2026, 5:56 a.m. |
Created at: May 3, 2026, 4:13 p.m.