Triple
T28856363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B-flat clarinet |
E728748
|
entity |
| Predicate | hasClef |
P27297
|
FINISHED |
| Object | treble clef |
—
|
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: treble clef | Statement: [B-flat clarinet, hasClef, treble clef]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClef Context triple: [B-flat clarinet, hasClef, treble clef]
-
A.
usesClef
chosen
Indicates that one entity employs or applies a particular clef in a musical notation context.
-
B.
hasKeySignature
Indicates that one musical work, passage, or notation is associated with a specific key signature defining its set of sharps or flats.
-
C.
hasTuningDivision
Indicates that one entity specifies or uses a particular system or scheme for dividing a range (such as a musical interval or scale) into tuning units.
-
D.
hasKeySignatureDistribution
Indicates that there is a specific pattern or spread of key signatures associated with the entity, describing how frequently or prominently different key signatures occur.
-
E.
hasFingeringSystem
Indicates that an instrument or object is associated with a particular method or system for positioning fingers to produce notes or actions.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 6:45 a.m.