Triple
T8290004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flip3D |
E193869
|
entity |
| Predicate | keyboardShortcut |
P82564
|
FINISHED |
| Object | Win+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: Win+Tab | Statement: [Flip3D, keyboardShortcut, Win+Tab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyboardShortcut Context triple: [Flip3D, keyboardShortcut, Win+Tab]
-
A.
keyAction
Indicates an action that is performed using a key, typically involving locking, unlocking, or otherwise operating a mechanism that requires a key.
-
B.
keyHitter
Indicates that an entity is a powerful or highly effective performer, especially in a competitive or performance-based context.
-
C.
keySymbol
Indicates that one entity serves as the symbolic representation or notation used to denote another entity as a key.
-
D.
keyLayout
Indicates the specific spatial arrangement and organization of keys or buttons within an input device or interface.
-
E.
keyThemeIn
Indicates that a particular theme is a central or primary thematic focus within a given work, context, or subject.
- F. None of above. chosen
Provenance (4 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c99fdd48190a3f304237be609a0 |
completed | March 31, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:52 p.m.