Triple
T38592426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blink (Overwatch ability) |
E932483
|
entity |
| Predicate | isSignatureMoveOf |
P108696
|
FINISHED |
| Object | Tracer (Overwatch) |
—
|
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: Tracer (Overwatch) | Statement: [Blink (Overwatch ability), isSignatureMoveOf, Tracer (Overwatch)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSignatureMoveOf Context triple: [Blink (Overwatch ability), isSignatureMoveOf, Tracer (Overwatch)]
-
A.
usesSignatureMove
chosen
Indicates that an entity performs or employs a distinctive, characteristic move or technique associated specifically with it.
-
B.
introducedAsSignatureMoveOf
Indicates that one entity was presented or established as the signature move or defining technique of another entity (such as a character, performer, or brand).
-
C.
isSignatureHitOf
Indicates that one hit or impact is the characteristic or defining strike associated with a particular entity, event, or performance.
-
D.
hasSignatureMechanic
Indicates that an entity (such as a game, character, or system) possesses a distinctive, defining mechanic or feature that is uniquely characteristic of it.
-
E.
isSignatureHitFor
Indicates that one event, action, or data pattern matches and triggers a specific predefined signature (such as a rule, template, or detection pattern).
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.