Triple
T37095536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 Overwatch League season |
E918549
|
entity |
| Predicate | previousGameVersion |
P22508
|
FINISHED |
| Object | Overwatch |
—
|
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: Overwatch | Statement: [2022 Overwatch League season, previousGameVersion, Overwatch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousGameVersion Context triple: [2022 Overwatch League season, previousGameVersion, Overwatch]
-
A.
previousVersionUsedFrom
Indicates that one entity was used as the immediately preceding version from which another entity was derived or updated.
-
B.
previousVersionInUseUntil
Indicates that an earlier version of something continued to be actively used up to a specified point in time.
-
C.
previousVersionAdopted
Indicates that one entity has been adopted or implemented as a successor to an earlier version represented by the other entity.
-
D.
predecessorVersion
chosen
Indicates that one entity is an earlier or prior version in a version sequence relative to another entity.
-
E.
previousVersionModified
Indicates that a newer version of an entity has been created by modifying the specified previous version.
- 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_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
Created at: May 3, 2026, 4:14 p.m.