Triple
T23425049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guild S-100 |
E560770
|
entity |
| Predicate | intonationAdjustment |
P78031
|
FINISHED |
| Object | adjustable bridge saddles |
—
|
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: adjustable bridge saddles | Statement: [Guild S-100, intonationAdjustment, adjustable bridge saddles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intonationAdjustment Context triple: [Guild S-100, intonationAdjustment, adjustable bridge saddles]
-
A.
pitchAlterationMechanism
chosen
Indicates the mechanism or method by which the pitch of a sound or signal is changed or controlled.
-
B.
tone
Indicates the characteristic attitude or emotional quality expressed in how something is communicated or presented.
-
C.
hasTonalityShift
Indicates a change in the tonal quality, mood, or key within a piece or segment, marking a shift from one tonality to another.
-
D.
voiceAppearance
Indicates that one entity’s voice is present, heard, or featured in association with another entity (such as a work, scene, or medium).
-
E.
tonalCharacteristic
Indicates the specific quality or character of a sound’s tone, such as its color, texture, or expressive nuance, in relation to an 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54951688190a3c5382971af3e41 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:47 p.m.