Triple
T38672025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Pro Keyboard |
E943621
|
entity |
| Predicate | hasKeySwitchType |
P9247
|
FINISHED |
| Object | rubber dome |
—
|
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: rubber dome | Statement: [Apple Pro Keyboard, hasKeySwitchType, rubber dome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeySwitchType Context triple: [Apple Pro Keyboard, hasKeySwitchType, rubber dome]
-
A.
hasKeyType
chosen
Indicates that an entity possesses or is associated with a specific category or type of key.
-
B.
hasKeyState
Indicates that an entity possesses or is associated with a particular key-related status or condition (such as pressed, released, enabled, or disabled).
-
C.
hasKeyMovement
Indicates that one entity possesses or defines the primary or characteristic movement pattern associated with another entity.
-
D.
hasKeyboardBy
Indicates that an entity is equipped with or uses a keyboard provided, installed, or controlled by another entity.
-
E.
hasFunctionKeys
Indicates that an object or device possesses dedicated keys assigned to specific functions or shortcuts.
- 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_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 3, 2026, 4:33 p.m.