Triple
T29326071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interlude (movement) |
E743645
|
entity |
| Predicate | hasParentWorkComposer |
P193940
|
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: [Interlude (movement), hasParentWorkComposer, Aaron Copland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentWorkComposer Context triple: [Interlude (movement), hasParentWorkComposer, Aaron Copland]
-
A.
hasParentWork
Indicates that one work is derived from, contained within, or otherwise subordinate to another, more primary work.
-
B.
hasParentWorkKey
Indicates that an entity is associated with the identifier (key) of the parent work from which it is derived or of which it is a part.
-
C.
hasComposerPreviousWork
Indicates that a composer has created an earlier work prior to the current one.
-
D.
basedOnWorkComposer
Indicates that one work is derived from, adapted from, or otherwise created on the basis of another work by the specified composer.
-
E.
followedByInComposerWork
Indicates that one element in a composer's work directly succeeds another in sequence within that same composition.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
| PDg | Predicate description generation | batch_69fd5bf49288819098a12202411cba4f |
completed | May 8, 2026, 3:43 a.m. |
Created at: April 28, 2026, 1:26 p.m.