Triple
T22953559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akai MPC60 |
E570087
|
entity |
| Predicate | padsType |
P150364
|
FINISHED |
| Object | velocity-sensitive pads |
—
|
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: velocity-sensitive pads | Statement: [Akai MPC60, padsType, velocity-sensitive pads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: padsType Context triple: [Akai MPC60, padsType, velocity-sensitive pads]
-
A.
pdsType
Indicates that an entity has or is classified by a specific Product Data Specification (PDS) type or category.
-
B.
PPAType
Indicates a specific type or category of a PPA (Power Purchase Agreement) relationship between parties.
-
C.
plateType
Indicates the specific category or style of plate associated with an item or context.
-
D.
hasPad
Indicates that one entity possesses, is equipped with, or is associated with a pad (such as a cushion, tablet, or protective surface).
-
E.
hasPadDesignation
Indicates that an entity is assigned or associated with a specific pad identifier or designation.
- 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181a34c30819099ff4812500a0991 |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:46 p.m.