Triple
T37095554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 Overwatch League season |
E918549
|
entity |
| Predicate | grandFinalsChampion |
P6604
|
FINISHED |
| Object | Dallas Fuel |
—
|
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: Dallas Fuel | Statement: [2022 Overwatch League season, grandFinalsChampion, Dallas Fuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grandFinalsChampion Context triple: [2022 Overwatch League season, grandFinalsChampion, Dallas Fuel]
-
A.
finalChampion
Indicates that an entity is the ultimate winner or last remaining champion in a competition or series of contests.
-
B.
finalsChampion
chosen
Indicates that an entity is the winner or champion of a particular final match, series, or tournament.
-
C.
finalChampions
Indicates that the related entities are the ultimate winners or title holders at the conclusion of a competition, season, or tournament.
-
D.
finalManagerOfChampion
Indicates that the subject is the ultimate or last manager responsible for the champion entity, typically at the time of its final or defining achievement.
-
E.
grandFinal
Indicates a culminating, decisive final event or match that determines the ultimate outcome or champion in a competition or series.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:14 p.m.