Triple
T22860375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonatas, Op. 40 |
E566901
|
entity |
| Predicate | associatedMusicalPeriod |
P38929
|
FINISHED |
| Object | Classical 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: Classical period | Statement: [Piano Sonatas, Op. 40, associatedMusicalPeriod, Classical period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMusicalPeriod Context triple: [Piano Sonatas, Op. 40, associatedMusicalPeriod, Classical period]
-
A.
musicalEra
chosen
Indicates the historical musical period or style with which an entity (such as a composition, performance, or musician) is associated.
-
B.
partOfCreativePeriod
Indicates that one creative work, phase, or output belongs to or occurs within a broader creative period or movement.
-
C.
musicalTheatreEra
Indicates the historical period or stylistic era of musical theatre with which an entity is associated.
-
D.
inMusicHistory
Indicates that something is recorded, referenced, or recognized within the context of music history.
-
E.
recordingEra
Indicates the historical time period or era during which the recording was made.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17ec082c08190943e6cfc2e25c5cc |
completed | April 29, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:37 p.m.