Triple
T37611543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regenlied Sonata |
E935795
|
entity |
| Predicate | originalKeyOfAssociatedSong |
P12877
|
FINISHED |
| Object | G minor |
—
|
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: G minor | Statement: [Regenlied Sonata, originalKeyOfAssociatedSong, G minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalKeyOfAssociatedSong Context triple: [Regenlied Sonata, originalKeyOfAssociatedSong, G minor]
-
A.
keyOfFirstSong
Indicates the musical key in which the first song in a sequence, collection, or recording is set.
-
B.
musicKey
chosen
Indicates the musical key in which a piece of music, passage, or section is composed or performed.
-
C.
keySongwriter
Indicates that the subject is the primary or main songwriter responsible for creating the song associated with the object.
-
D.
associatedKey
Indicates that one entity serves as a key or identifier that is logically or functionally linked to another entity.
-
E.
associatedWithSongTheme
Indicates a relationship where something is linked or connected to the thematic content or subject matter of a song.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.