Triple
T38672017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Pro Keyboard |
E943621
|
entity |
| Predicate | hasModifierKeys |
P201192
|
FINISHED |
| Object | Command key |
—
|
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: Command key | Statement: [Apple Pro Keyboard, hasModifierKeys, Command key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModifierKeys Context triple: [Apple Pro Keyboard, hasModifierKeys, Command key]
-
A.
hasKeyEvent
Indicates that an entity includes, is associated with, or is characterized by a significant or defining event.
-
B.
hasFunctionKeys
Indicates that an object or device possesses dedicated keys assigned to specific functions or shortcuts.
-
C.
hasKeyBinding
Indicates that a control, command, or action is associated with a specific key or key combination as its input trigger.
-
D.
hasSeparateCursorKeys
Indicates that a device or interface provides distinct, dedicated cursor (arrow) keys separate from other keys.
-
E.
hasKeyboardBy
Indicates that an entity is equipped with or uses a keyboard provided, installed, or controlled by another entity.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffdd05d1908190957deb11392f4595 |
completed | May 10, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69ffdc0d33c881908b3483bee8a96540 |
completed | May 10, 2026, 1:14 a.m. |
| PDg | Predicate description generation | batch_69ffdd0486e08190a0f2ff4ce0aee13b |
completed | May 10, 2026, 1:19 a.m. |
Created at: May 3, 2026, 4:33 p.m.