Triple
T4514905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violin Sonata No. 9 in A major, Op. 47 |
E102130
|
entity |
| Predicate | inKeyOfMovement2 |
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: [Violin Sonata No. 9 in A major, Op. 47, inKeyOfMovement2, F major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inKeyOfMovement2 Context triple: [Violin Sonata No. 9 in A major, Op. 47, inKeyOfMovement2, F major]
-
A.
secondMovementKey
chosen
Indicates the musical key in which the second movement of a multi-movement work is composed.
-
B.
movement1Key
Indicates a relationship where an entity’s primary or defining movement action or motion pattern is specified or referenced.
-
C.
movement2Key
Indicates a mapping or correspondence between a specific movement and its associated key (such as a musical key, identifier, or control).
-
D.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
E.
movement3Key
Indicates a three-part or third-level categorization of how an entity moves or changes location relative to another entity or reference point.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5725745c81908bb462ba9537ae14 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.