Triple
T37898606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonata No. 15 in D major, Op. 28 "Pastoral" |
E945345
|
entity |
| Predicate | hasFormInFourthMovement |
P86653
|
FINISHED |
| Object | rondo form |
—
|
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: rondo form | Statement: [Piano Sonata No. 15 in D major, Op. 28 "Pastoral", hasFormInFourthMovement, rondo form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormInFourthMovement Context triple: [Piano Sonata No. 15 in D major, Op. 28 "Pastoral", hasFormInFourthMovement, rondo form]
-
A.
fourthMovementForm
chosen
Indicates that one entity is the formal structure or type of the fourth movement within a larger multi-movement work associated with another entity.
-
B.
tonalityOfFourthMovement
Indicates the key or tonal center used in the fourth movement of a musical work.
-
C.
fourthMovementTitle
Indicates the title or name given to the fourth movement of a multi-movement musical work.
-
D.
movementNumberInSymphonyNo4
Indicates the specific movement number that a given movement occupies within Symphony No. 4.
-
E.
hasScherzoMovement
Indicates that a musical work includes a scherzo as one of its movements.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
Created at: May 3, 2026, 4:19 p.m.