Triple
T9018103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KRunner |
E215644
|
entity |
| Predicate | defaultShortcut |
P82564
|
FINISHED |
| Object | Alt+Space |
—
|
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: Alt+Space | Statement: [KRunner, defaultShortcut, Alt+Space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultShortcut Context triple: [KRunner, defaultShortcut, Alt+Space]
-
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.
defaultBehavior
Indicates the standard or fallback way an entity acts or responds when no specific or overriding instructions or conditions are provided.
-
C.
defaultOn
Indicates that something is in an enabled or active state by default, without requiring explicit activation.
-
D.
defaultRemote
Indicates that one entity is designated as the primary or standard remote counterpart used by another entity for communication, synchronization, or access.
-
E.
canonicalFocus
Indicates that one entity is the primary or most representative focus or point of attention in relation to another entity.
- 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a3ef98081909e66372a89f881b9 |
completed | April 1, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.