Triple
T28390653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flip 3D |
E719147
|
entity |
| Predicate | defaultToggleKey |
P82564
|
FINISHED |
| Object | Windows key + Tab |
—
|
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: Windows key + Tab | Statement: [Flip 3D, defaultToggleKey, Windows key + Tab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultToggleKey Context triple: [Flip 3D, defaultToggleKey, Windows key + Tab]
-
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.
keyboardFeature
Indicates that one entity is a feature, characteristic, or functional attribute of a keyboard.
-
D.
keyAction
Indicates an action that is performed using a key, typically involving locking, unlocking, or otherwise operating a mechanism that requires a key.
-
E.
keyHitter
Indicates that an entity is a powerful or highly effective performer, especially in a competitive or performance-based context.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 28, 2026, 1:13 a.m.