Triple
T37010595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 Overwatch League season |
E915931
|
entity |
| Predicate | allStarRegion |
P16438
|
FINISHED |
| Object | Asia All-Stars |
—
|
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: Asia All-Stars | Statement: [2020 Overwatch League season, allStarRegion, Asia All-Stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allStarRegion Context triple: [2020 Overwatch League season, allStarRegion, Asia All-Stars]
-
A.
rankingRegion
Indicates the geographic or administrative region within which a ranking or ordered comparison of entities is defined or evaluated.
-
B.
clubRegion
Indicates that a club is located in, associated with, or belongs to a particular geographic region.
-
C.
participantsRegion
chosen
Indicates that the related entities are associated with, originate from, or operate within a specified geographic region.
-
D.
teamSportGoverningBodyRegion
Indicates the geographic region or jurisdiction within which a governing body oversees or regulates a particular team sport.
-
E.
playerBaseRegion
Indicates the geographic region or area that serves as the primary base or home location for a player.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.