Triple
T11775416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opus 27 No. 2 |
E280004
|
entity |
| Predicate | formOfThirdMovement |
P83105
|
FINISHED |
| Object | sonata-allegro 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: sonata-allegro form | Statement: [Opus 27 No. 2, formOfThirdMovement, sonata-allegro form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formOfThirdMovement Context triple: [Opus 27 No. 2, formOfThirdMovement, sonata-allegro form]
-
A.
typicalFormOfThirdMovement
chosen
Indicates the characteristic or standard structural pattern commonly used for the third movement within a larger multi-movement work.
-
B.
tonalityOfThirdMovement
Indicates the key or tonal center that characterizes the third movement of a musical work.
-
C.
characterOfThirdMovement
Indicates that something specifies the musical or expressive character of the third movement of a larger work.
-
D.
fourthMovementForm
Indicates that one entity is the formal structure or type of the fourth movement within a larger multi-movement work associated with another entity.
-
E.
formOfFinalMovement
Indicates that one movement serves as the concluding or final section of another movement or larger musical work.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:42 p.m.