Triple
T38672014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Pro Keyboard |
E943621
|
entity |
| Predicate | hasMediaKeys |
P116999
|
FINISHED |
| Object | volume control keys |
—
|
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: volume control keys | Statement: [Apple Pro Keyboard, hasMediaKeys, volume control keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMediaKeys Context triple: [Apple Pro Keyboard, hasMediaKeys, volume control keys]
-
A.
hasDedicatedMediaKeys
chosen
Indicates that an input device includes specific keys assigned to control media functions (such as play, pause, volume, or track navigation).
-
B.
hasKeySystem
Indicates that an entity possesses, uses, or is associated with a particular key-based system (such as for access control, encryption, or identification).
-
C.
keySystem
Indicates a relationship where one entity functions as the primary or controlling system that governs, secures, or coordinates access to another entity or set of entities.
-
D.
supportsDRMViaContainer
Indicates that one entity enables or provides digital rights management (DRM) functionality through the use of a specific container format or packaging mechanism.
-
E.
supportsMediaManagement
Indicates that one entity provides functionality or assistance for organizing, handling, or controlling media content for another entity.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:33 p.m.