Triple
T26845142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missa Mille Regretz |
E675894
|
entity |
| Predicate | derivesMelodicMaterialFrom |
P37245
|
FINISHED |
| Object | Mille regretz (chanson) |
—
|
NE NERFINISHED |
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: Mille regretz (chanson) | Statement: [Missa Mille Regretz, derivesMelodicMaterialFrom, Mille regretz (chanson)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivesMelodicMaterialFrom Context triple: [Missa Mille Regretz, derivesMelodicMaterialFrom, Mille regretz (chanson)]
-
A.
melodicPattern
Indicates a recurring sequence of musical tones or intervals that forms a recognizable melodic structure within a piece.
-
B.
isMelodic
Indicates that something possesses a tuneful, harmonious, or musically pleasing quality.
-
C.
hasMoreMelodicSoundThan
Indicates that the sound produced by one entity is judged to be more melodic, tuneful, or musically pleasing than the sound produced by another entity.
-
D.
hasMelody
Indicates that one entity possesses, contains, or is characterized by a particular melody.
-
E.
melodyReusedBy
chosen
Indicates that a melody originally used in one work is later reused or incorporated in another work.
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 5:11 a.m.