Triple
T38044144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonata No. 20 in G major, Op. 49 No. 2 |
E949568
|
entity |
| Predicate | compositionPeriodRelativeToComposer |
P6964
|
FINISHED |
| Object | early 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: early period | Statement: [Piano Sonata No. 20 in G major, Op. 49 No. 2, compositionPeriodRelativeToComposer, early period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compositionPeriodRelativeToComposer Context triple: [Piano Sonata No. 20 in G major, Op. 49 No. 2, compositionPeriodRelativeToComposer, early period]
-
A.
periodOfComposer
Indicates the historical or stylistic period during which a composer was active or to which their work is primarily associated.
-
B.
dateOfComposition
chosen
Indicates the calendar date or time period when a particular work was created or composed.
-
C.
spanOfCompositionYears
Indicates the range of years during which a composition was created or worked on.
-
D.
compositionYear
Indicates the year in which a work (such as a piece of music, art, or literature) was originally created or composed.
-
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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: May 3, 2026, 4:20 p.m.