Triple
T24280070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | erhu |
E605511
|
entity |
| Predicate | isSoundModifiedBy |
P155677
|
FINISHED |
| Object | left-hand finger pressure without fingerboard |
—
|
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: left-hand finger pressure without fingerboard | Statement: [erhu, isSoundModifiedBy, left-hand finger pressure without fingerboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSoundModifiedBy Context triple: [erhu, isSoundModifiedBy, left-hand finger pressure without fingerboard]
-
A.
containsSound
Indicates that one entity includes, embodies, or produces the sound associated with another entity.
-
B.
includesAddedSound
Indicates that one entity contains or incorporates an additional sound element beyond the original or primary audio content.
-
C.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
D.
usesSound
Indicates that one entity employs or relies on sound as a means or tool in relation to another entity or context.
-
E.
usesSoundMaterial
Indicates that an entity employs or incorporates sound-based materials (such as audio, recordings, or sonic elements) in its activity, process, or composition.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f51050481908a9bd3c586702057 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 18, 2026, 12:07 a.m.