Triple
T38080554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waldstein Sonata |
E950839
|
entity |
| Predicate | keySecondMovement |
P40265
|
FINISHED |
| Object | F major |
—
|
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: F major | Statement: [Waldstein Sonata, keySecondMovement, F major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keySecondMovement Context triple: [Waldstein Sonata, keySecondMovement, F major]
-
A.
secondMovementKey
chosen
Indicates the musical key in which the second movement of a multi-movement work is composed.
-
B.
secondMovementFeature
Indicates that the subject is characterized by or associated with a specific feature of the second movement within a larger sequence or structure.
-
C.
keyOfMovement7
Indicates a specific key or control input that triggers or corresponds to the seventh defined type of movement in a system.
-
D.
thirdMovementKey
Indicates the musical key in which the third movement of a multi-movement work is composed or performed.
-
E.
secondMovementForm
Indicates that an entity is in the form or structure of the second movement within a larger multi-movement work or sequence.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.