Triple
T29998878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieder by Felix Mendelssohn |
E762106
|
entity |
| Predicate | setsToMusic |
P78347
|
FINISHED |
| Object | Romantic poetry |
—
|
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: Romantic poetry | Statement: [Lieder by Felix Mendelssohn, setsToMusic, Romantic poetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsToMusic Context triple: [Lieder by Felix Mendelssohn, setsToMusic, Romantic poetry]
-
A.
setToMusicAs
chosen
Indicates that one entity (typically a text or work) has been adapted and arranged by another entity into a musical composition.
-
B.
setToMusicIn
Indicates that something (typically text or lyrics) has been arranged or adapted to be performed as music within a particular work or context.
-
C.
settingInMusical
Indicates that one entity serves as the setting or location in which the events of a musical take place.
-
D.
musicMotif
Indicates a recurring musical idea, theme, or pattern that appears multiple times within a composition or across related works.
-
E.
settingInspiresMusic
Indicates that a particular setting or environment serves as the inspiration or creative source for a piece of music.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6794cf5848190a60ca2c4d9f50098 |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:40 p.m.