Triple
T37095541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 Overwatch League season |
E918549
|
entity |
| Predicate | featuredHero |
P36250
|
FINISHED |
| Object | Sojourn |
E932541
|
NE 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: Sojourn | Statement: [2022 Overwatch League season, featuredHero, Sojourn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredHero Context triple: [2022 Overwatch League season, featuredHero, Sojourn]
-
A.
featuresHero
chosen
Indicates that something (such as a work, product, or story) prominently includes or centers around a particular hero as a main character or focus.
-
B.
featuredElement
Indicates that one element is highlighted or given special prominence relative to others in a given context.
-
C.
featuredFor
Indicates that one entity is highlighted, promoted, or specially showcased in the context or for the benefit of another entity.
-
D.
featuredArea
Indicates that an area or section is highlighted or given special prominence within a larger context or layout.
-
E.
featuredOn
Indicates that one entity is prominently presented, highlighted, or showcased on or within another entity (such as a platform, publication, or product).
- F. None of above.
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_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3efdd08da481909aa66f655cf0c6c3 |
completed | June 26, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.