Triple
T31528255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prokofiev piano sonatas |
E804402
|
entity |
| Predicate | spanOfCompositionYears |
P172270
|
FINISHED |
| Object | 1907–1947 |
—
|
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: 1907–1947 | Statement: [Prokofiev piano sonatas, spanOfCompositionYears, 1907–1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spanOfCompositionYears Context triple: [Prokofiev piano sonatas, spanOfCompositionYears, 1907–1947]
-
A.
seasonSpan
Indicates the time period or range of dates over which a particular season extends or is in effect.
-
B.
periodOfComposer
Indicates the historical or stylistic period during which a composer was active or to which their work is primarily associated.
-
C.
spansDecadesTo
Indicates that something extends continuously across multiple decades up to a specified later point in time.
-
D.
timeInArtistCareer
Indicates the point or period within an artist’s professional career at which a given event, work, or activity occurs.
-
E.
compositionYear
Indicates the year in which a work (such as a piece of music, art, or literature) was originally created or composed.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 30, 2026, 9:59 p.m.