Triple
T9018101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KRunner |
E215644
|
entity |
| Predicate | invocationMethod |
P39337
|
FINISHED |
| Object | keyboard shortcut |
—
|
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: keyboard shortcut | Statement: [KRunner, invocationMethod, keyboard shortcut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invocationMethod Context triple: [KRunner, invocationMethod, keyboard shortcut]
-
A.
invocationOf
Indicates that one entity is the act, event, or instance of calling upon, summoning, or appealing to another entity (such as a function, service, or authority) to perform its role or be brought into effect.
-
B.
invocationType
chosen
Indicates the manner or mode in which an action, function, or process is called, triggered, or executed.
-
C.
invokedIn
Indicates that an action, method, or function is called or executed within the context or body of another construct (such as a method, block, or scope).
-
D.
canBeInvokedBy
Indicates that one entity (such as a function, method, or operation) is able to be called, triggered, or executed by another entity.
-
E.
keyInvocation
Indicates that an entity triggers or calls a specific key-related operation or function.
- 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.