Triple
T30889247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Study for String Orchestra |
E786850
|
entity |
| Predicate | survivingWorkOfComposer |
P40533
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Study for String Orchestra, survivingWorkOfComposer, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingWorkOfComposer Context triple: [Study for String Orchestra, survivingWorkOfComposer, true]
-
A.
dedicatedComposerWork
Indicates that a particular work was specifically created or formally dedicated by the composer to a person, group, or entity.
-
B.
partOfComposerOeuvre
chosen
Indicates that a musical work belongs to and is included within the overall body of compositions created by a particular composer.
-
C.
isRelatedWorkOfComposer
Indicates that one work is associated with or connected to a particular composer, typically as a composition created by that composer.
-
D.
producedComposer
Indicates that one entity served as the producer for a musical work created or composed by another entity.
-
E.
completedInYearOfComposerDeath
Indicates that a work was completed in the same calendar year that its composer died.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69207e29081909ecef6eabcd3f2d1 |
completed | May 3, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:49 p.m.