Triple
T35281327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorymoog |
E1018940
|
entity |
| Predicate | aftertouchSupport |
P151640
|
FINISHED |
| Object | no aftertouch |
—
|
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 aftertouch | Statement: [Memorymoog, aftertouchSupport, no aftertouch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aftertouchSupport Context triple: [Memorymoog, aftertouchSupport, no aftertouch]
-
A.
supportsAftertouch
chosen
Indicates that an entity is capable of responding to or processing aftertouch (pressure-based) input that occurs after an initial activation.
-
B.
supportedAfter
Indicates that one entity provided support to another only after a specified event, time, or condition had occurred.
-
C.
touchesState
Indicates that one entity is in physical contact with, or directly affects, the state or condition of another entity.
-
D.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
-
E.
supportsTapOnTapOff
Indicates that a system or service allows users to initiate and complete interactions or transactions by tapping a device or card at both the start and end of use.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.