Triple
T37039444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 Overwatch League season |
E916738
|
entity |
| Predicate | introducedFormatElement |
P42254
|
FINISHED |
| Object | regional tournaments |
—
|
LITERAL FINISHED |
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: regional tournaments | Statement: [2021 Overwatch League season, introducedFormatElement, regional tournaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedFormatElement Context triple: [2021 Overwatch League season, introducedFormatElement, regional tournaments]
-
A.
hasFormatElement
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
-
B.
formatIntroduced
chosen
Indicates that a particular format was first introduced or made available at a specific time or in a specific context.
-
C.
presentedInFormat
Indicates that something is expressed, delivered, or made available using a particular format or representation.
-
D.
definesFormatFor
Indicates that one entity specifies or establishes the format or structural pattern to be used by another entity.
-
E.
createdFormatThatBecame
Indicates that one entity created a format which later evolved into or was adopted as another specified format.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: May 3, 2026, 4:14 p.m.