Triple
T11590217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E major (BWV 1006) |
E274860
|
entity |
| Predicate | keySignature |
P83458
|
FINISHED |
| Object | four sharps |
—
|
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: four sharps | Statement: [E major (BWV 1006), keySignature, four sharps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keySignature Context triple: [E major (BWV 1006), keySignature, four sharps]
-
A.
hasKeySignature
chosen
Indicates that one musical work, passage, or notation is associated with a specific key signature defining its set of sharps or flats.
-
B.
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.
-
C.
musicKey
Indicates the musical key in which a piece of music, passage, or section is composed or performed.
-
D.
musicalSymbol
Indicates that one entity is a musical notation mark or sign associated with another entity in a musical context.
-
E.
musicTheoryContext
Indicates that one entity is interpreted or analyzed within the framework, rules, or concepts of music theory in relation to another entity or situation.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d894643ae48190837502b713f5b9c6 |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.