Triple
T23582247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurzweil K250 |
E582236
|
entity |
| Predicate | keyboardAction |
P84135
|
FINISHED |
| Object | weighted keyboard |
—
|
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: weighted keyboard | Statement: [Kurzweil K250, keyboardAction, weighted keyboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyboardAction Context triple: [Kurzweil K250, keyboardAction, weighted keyboard]
-
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.
keyActionType
Indicates the specific kind of action or operation being performed or associated with a key.
-
C.
keyHitter
Indicates that an entity is a powerful or highly effective performer, especially in a competitive or performance-based context.
-
D.
keyboardFeature
chosen
Indicates that one entity is a feature, characteristic, or functional attribute of a keyboard.
-
E.
keyboardShortcut
Indicates that one entity is a keyboard key combination used to trigger or activate the function, command, or action represented by 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02cf4e0819094ff4e406cda270d |
completed | April 29, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:40 p.m.