Triple
T15191631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Variations on a Theme |
E363023
|
entity |
| Predicate | workTitleType |
P117066
|
FINISHED |
| Object | descriptive musical title |
—
|
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: descriptive musical title | Statement: [Variations on a Theme, workTitleType, descriptive musical title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workTitleType Context triple: [Variations on a Theme, workTitleType, descriptive musical title]
-
A.
workTitle
Indicates the formal title or name of a work (such as a book, artwork, or composition) associated with an entity.
-
B.
workTitleContains
Indicates that the title of a work includes a specified substring or term.
-
C.
workTitleWithOpus
Indicates that a work’s title is associated with a specific opus number designation.
-
D.
workFromWhichTitleDerived
Indicates that a title is derived from, or based on, a particular underlying work.
-
E.
basedOnWorkTitle
Indicates that something is derived from, adapted from, or otherwise created based on a work identified by its title.
- F. None of above. chosen
Provenance (4 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0067d55ac8190b7a7fce36e6ddf3c |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:10 a.m.