Triple
T29655257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warp Gate |
E750245
|
entity |
| Predicate | hotkeyDefault |
P82564
|
FINISHED |
| Object | W (in standard StarCraft II hotkeys) |
—
|
LITERAL 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: W (in standard StarCraft II hotkeys) | Statement: [Warp Gate, hotkeyDefault, W (in standard StarCraft II hotkeys)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hotkeyDefault Context triple: [Warp Gate, hotkeyDefault, W (in standard StarCraft II hotkeys)]
-
A.
keyboardShortcut
chosen
Indicates that one entity is a keyboard key combination used to trigger or activate the function, command, or action represented by another entity.
-
B.
keyboardShortcutAlternative
Indicates an alternative keyboard shortcut that can be used to perform the same action or command as another shortcut.
-
C.
settingOfKeyEvent
Indicates that a particular location or context is where a key or pivotal event takes place.
-
D.
keyHitter
Indicates that an entity is a powerful or highly effective performer, especially in a competitive or performance-based context.
-
E.
hasShortcuts
Indicates that an entity provides or supports shortcut actions or quick-access commands to perform operations more efficiently.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f274ba08190bcdbdfeccf4af09d |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:54 p.m.