Triple
T35281429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sub 37 |
E1018942
|
entity |
| Predicate | hasAftertouch |
P151640
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sub 37, hasAftertouch, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAftertouch Context triple: [Sub 37, hasAftertouch, true]
-
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.
hasArpeggiator
Indicates that an entity includes or is associated with an arpeggiator function or component.
-
C.
hasKeyReleases
Indicates that an entity is associated with specific key releases, such as major versions, milestones, or important publication events in its lifecycle.
-
D.
hasFingeringSystem
Indicates that an instrument or object is associated with a particular method or system for positioning fingers to produce notes or actions.
-
E.
hasPedalboardRange
Indicates the range of notes or pitches that can be played using a pedalboard.
- 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_69f78fdaeaf88190a6b24a96634ddfe1 |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.