Triple
T13230026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugue in F major, BWV 856 |
E314987
|
entity |
| Predicate | hasNotatedClefs |
P27297
|
FINISHED |
| Object | treble and bass clefs |
—
|
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 and bass clefs | Statement: [Fugue in F major, BWV 856, hasNotatedClefs, treble and bass clefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotatedClefs Context triple: [Fugue in F major, BWV 856, hasNotatedClefs, treble and bass clefs]
-
A.
hasKeySignature
Indicates that one musical work, passage, or notation is associated with a specific key signature defining its set of sharps or flats.
-
B.
usesClef
chosen
Indicates that one entity employs or applies a particular clef in a musical notation context.
-
C.
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.
-
D.
usesInterpretiveStaff
Indicates that an entity relies on interpretive staff (such as guides, educators, or docents) to convey information, context, or explanations about something to an audience.
-
E.
hasFrequencyNote
Indicates that something is associated with a specific note describing how often it occurs or is repeated.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d336ae08190bfc118cfbefddf84 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:21 p.m.