Triple

T28613899
Position Surface form Disambiguated ID Type / Status
Subject Windows Mobility Center E724231 entity
Predicate supportsHotkeys P118542 FINISHED
Object no direct global hotkeys per tile 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: no direct global hotkeys per tile | Statement: [Windows Mobility Center, supportsHotkeys, no direct global hotkeys per tile]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsHotkeys
Context triple: [Windows Mobility Center, supportsHotkeys, no direct global hotkeys per tile]
  • A. supportsKeyboard
    Indicates that one entity is compatible with or able to be operated using a keyboard as an input method.
  • B. supportsKeymap
    Indicates that one entity is compatible with and can operate using a specified keymap configuration.
  • C. hasShortcuts chosen
    Indicates that an entity provides or supports shortcut actions or quick-access commands to perform operations more efficiently.
  • D. supportsKeyboardAndMouse
    Indicates that the subject provides compatibility with and can be operated using both a keyboard and a mouse.
  • E. keySupportFrom
    Indicates that one entity provides essential backing, endorsement, or assistance that is crucial for the success or continuation of another entity or action.
  • 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_69f01d816d7c8190a1fe27e3434041dc completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_6a014f7602988190b8f86cb431a9cf12 completed May 11, 2026, 3:39 a.m.
PD Predicate disambiguation batch_6a014a70ea748190bd86fb9f218103ba completed May 11, 2026, 3:18 a.m.
Created at: April 28, 2026, 4:31 a.m.