Triple
T37095544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 Overwatch League season |
E918549
|
entity |
| Predicate | hadStage |
P187136
|
FINISHED |
| Object | Kickoff Clash |
—
|
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: Kickoff Clash | Statement: [2022 Overwatch League season, hadStage, Kickoff Clash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadStage Context triple: [2022 Overwatch League season, hadStage, Kickoff Clash]
-
A.
hasStageIn
Indicates a relationship where one entity occurs, exists, or takes place within a particular stage or phase of another process, lifecycle, or sequence.
-
B.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
C.
hadChapterAt
Indicates that an organization or group maintained an official chapter, branch, or local unit at a specified location or institution.
-
D.
hasStageHouse
Indicates that a performance venue or theater includes or is equipped with a stage house as part of its structure.
-
E.
usedStage
Indicates that an entity made use of a particular stage or phase within a process, workflow, or lifecycle.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:14 p.m.