Triple
T11543330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overwatch: Anthology |
E273724
|
entity |
| Predicate | featuresCharacter |
P626
|
FINISHED |
| Object | Torbjörn |
E912267
|
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: Torbjörn | Statement: [Overwatch: Anthology, featuresCharacter, Torbjörn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Torbjörn Context triple: [Overwatch: Anthology, featuresCharacter, Torbjörn]
-
A.
Torbjørn
chosen
Torbjørn is a Scandinavian masculine given name, particularly common in Norway, derived from Old Norse elements meaning "Thor" and "bear."
-
B.
Ingvar
Ingvar is a Scandinavian given name of Old Norse origin, historically associated with Viking-age figures and meaning roughly "Ing’s warrior" or "warrior of the god Ing."
-
C.
Geir
Geir is a masculine given name of Old Norse origin, commonly used in Scandinavian countries and meaning "spear."
-
D.
Göran
Göran is a Swedish masculine given name, commonly used in Sweden and borne by various notable figures.
-
E.
Einar
Einar is a masculine given name of Norse origin commonly used in Scandinavian countries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e1d754819089f3b6be3404fa0b |
completed | April 10, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e685bbb0cc8190b60a1eea13a3b423 |
completed | April 20, 2026, 7:59 p.m. |
Created at: April 8, 2026, 9:37 p.m.