Triple
T32742456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Der Abschied |
E837251
|
entity |
| Predicate | associatedComposerLifePeriod |
P102663
|
FINISHED |
| Object | Mahler's late creative period |
—
|
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: Mahler's late creative period | Statement: [Der Abschied, associatedComposerLifePeriod, Mahler's late creative period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedComposerLifePeriod Context triple: [Der Abschied, associatedComposerLifePeriod, Mahler's late creative period]
-
A.
periodOfComposer
chosen
Indicates the historical or stylistic period during which a composer was active or to which their work is primarily associated.
-
B.
composerBirthYear
Indicates the year in which a composer was born.
-
C.
creatorLifespan
Indicates the time period between the birth and death of the creator associated with an entity.
-
D.
associatedWithComposerEra
Indicates a relationship where a composer is linked to a particular historical musical era or stylistic period.
-
E.
spanOfCompositionYears
Indicates the range of years during which a composition was created or worked on.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:12 a.m.