Triple
T29854136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 1 in C major (Moments musicaux, D. 780) |
E758139
|
entity |
| Predicate | associatedComposerLifespan |
P27074
|
FINISHED |
| Object | 1797–1828 |
—
|
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: 1797–1828 | Statement: [No. 1 in C major (Moments musicaux, D. 780), associatedComposerLifespan, 1797–1828]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedComposerLifespan Context triple: [No. 1 in C major (Moments musicaux, D. 780), associatedComposerLifespan, 1797–1828]
-
A.
periodOfComposer
Indicates the historical or stylistic period during which a composer was active or to which their work is primarily associated.
-
B.
creatorLifespan
chosen
Indicates the time period between the birth and death of the creator associated with an entity.
-
C.
spanOfCompositionYears
Indicates the range of years during which a composition was created or worked on.
-
D.
associatedWithComposerEra
Indicates a relationship where a composer is linked to a particular historical musical era or stylistic period.
-
E.
composerBirthYear
Indicates the year in which a composer was born.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 5:45 p.m.