Triple
T37095561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 Overwatch League season |
E918549
|
entity |
| Predicate | hadRunnerUp |
P156725
|
FINISHED |
| Object | San Francisco Shock |
—
|
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: San Francisco Shock | Statement: [2022 Overwatch League season, hadRunnerUp, San Francisco Shock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRunnerUp Context triple: [2022 Overwatch League season, hadRunnerUp, San Francisco Shock]
-
A.
runnerUp
Indicates that one entity finished in second place relative to another in a competition or ranking.
-
B.
runnerUpWins
Indicates that an entity finishes in second place in a competition or ranking and receives the corresponding runner-up victory or award.
-
C.
hasRunnerUpTeam
chosen
Indicates that an entity (such as a competition or event) is associated with the team that finished in second place.
-
D.
hasNationalRunnerUpFinishes
Indicates that an entity has achieved one or more second-place (runner-up) finishes in a national-level competition or championship.
-
E.
runnerUpDriver
Indicates that one driver finished in second place relative to others in a race or competition.
- 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_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.