Triple
T21249147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ballad of Sweeney Todd |
E523694
|
entity |
| Predicate | functionInMusical |
P26917
|
FINISHED |
| Object | prologue |
—
|
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: prologue | Statement: [The Ballad of Sweeney Todd, functionInMusical, prologue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInMusical Context triple: [The Ballad of Sweeney Todd, functionInMusical, prologue]
-
A.
musicalFunction
Indicates the specific role or function an entity plays within a musical context, such as its harmonic, structural, or performative purpose in a piece or performance.
-
B.
songFunction
chosen
Indicates the role or purpose a song serves within a larger context, such as a performance, narrative, or musical structure.
-
C.
musicalMode
Indicates the specific tonal framework or scale system (mode) in which a piece of music or musical passage is organized.
-
D.
lyricalFunction
Indicates the role or purpose that lyrics serve within a musical or poetic work, such as narrating, expressing emotion, or structuring the piece.
-
E.
settingInMusical
Indicates that one entity serves as the setting or location in which the events of a musical take place.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359c7a648190b4345336ac3be024 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:56 p.m.