Triple
T1934024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sturm und Drang |
E41405
|
entity |
| Predicate | musicStyleCharacteristic |
P22764
|
FINISHED |
| Object | minor keys |
—
|
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: minor keys | Statement: [Sturm und Drang, musicStyleCharacteristic, minor keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicStyleCharacteristic Context triple: [Sturm und Drang, musicStyleCharacteristic, minor keys]
-
A.
notableSongCharacteristic
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
-
B.
hasSongStyle
Indicates that an entity possesses, is characterized by, or is associated with a particular style or genre of song.
-
C.
includesMusicalStyle
chosen
Indicates that one entity encompasses, features, or incorporates a particular musical style as part of its content or character.
-
D.
musicalMode
Indicates the specific tonal framework or scale system (mode) in which a piece of music or musical passage is organized.
-
E.
genreRecognized
Indicates that a particular genre has been identified or acknowledged as applicable 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb29b51408190afb2f918814e68c7 |
completed | March 7, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.