Triple
T27773892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peer Gynt Suite No. 2 |
E699131
|
entity |
| Predicate | hasKeyMovementsWithVocalOrigin |
P33166
|
FINISHED |
| Object | Solveig’s Song |
—
|
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: Solveig’s Song | Statement: [Peer Gynt Suite No. 2, hasKeyMovementsWithVocalOrigin, Solveig’s Song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyMovementsWithVocalOrigin Context triple: [Peer Gynt Suite No. 2, hasKeyMovementsWithVocalOrigin, Solveig’s Song]
-
A.
hasVocalPartInMovement
chosen
Indicates that a vocal part is present and participates in a specific movement of a larger musical work.
-
B.
hasVocalCharacter
Indicates that an entity possesses a particular vocal quality, style, or characteristic in its sound or voice.
-
C.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
D.
hasBackwardVocals
Indicates that the subject uses or contains backward (reversed) vocal audio in relation to the object.
-
E.
hasMusicalVocalType
Indicates that an entity is associated with a specific type or classification of singing voice.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 5:04 p.m.