Triple
T29325590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fanfare for the Uncommon Woman |
E743632
|
entity |
| Predicate | inspiredByComposer |
P31037
|
FINISHED |
| Object | Aaron Copland |
—
|
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: Aaron Copland | Statement: [Fanfare for the Uncommon Woman, inspiredByComposer, Aaron Copland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredByComposer Context triple: [Fanfare for the Uncommon Woman, inspiredByComposer, Aaron Copland]
-
A.
inspiredByArtist
chosen
Indicates that one entity’s work, style, or creation is influenced or motivated by the artistic output or persona of another artist.
-
B.
favoriteComposer
Indicates that one entity is the preferred or most liked composer of another entity.
-
C.
homageToComposer
Indicates that one entity pays tribute or respect to a composer, often by referencing, honoring, or being inspired by their work.
-
D.
hasMusicalComposer
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
E.
composedForMusicBy
Indicates that a musical work was specifically created or written by a particular composer.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 1:26 p.m.