Triple
T21981349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony in D minor |
E542846
|
entity |
| Predicate | usesMotivicTransformation |
P90320
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Symphony in D minor, usesMotivicTransformation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMotivicTransformation Context triple: [Symphony in D minor, usesMotivicTransformation, true]
-
A.
transformationMotif
Indicates a recurring pattern or theme in which one entity undergoes a change in form, state, or identity in relation to another.
-
B.
usesMotifsFrom
Indicates that one entity incorporates or draws upon recurring themes, patterns, or elements that originate from another entity.
-
C.
hasMotivicFunction
Indicates that one musical element serves a specific thematic or structural role in relation to a larger motive or passage.
-
D.
usesCantusFirmus
Indicates that one musical element is based on or incorporates a pre-existing cantus firmus melody as its structural foundation.
-
E.
usesTransformation
chosen
Indicates that one entity applies or relies on a specific transformation process, method, or function to operate on or convert another 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1248de3688190a8d24cc8458851f2 |
completed | April 28, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:04 p.m.