Triple
T8602517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Schumann: Fantasiestücke, Op. 12 |
E203712
|
entity |
| Predicate | keyOfMovement2 |
P39542
|
FINISHED |
| Object | F minor |
—
|
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 minor | Statement: [Robert Schumann: Fantasiestücke, Op. 12, keyOfMovement2, F minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyOfMovement2 Context triple: [Robert Schumann: Fantasiestücke, Op. 12, keyOfMovement2, F minor]
-
A.
secondMovementKey
Indicates the musical key in which the second movement of a multi-movement work is composed.
-
B.
movement2Key
chosen
Indicates a mapping or correspondence between a specific movement and its associated key (such as a musical key, identifier, or control).
-
C.
movement1Key
Indicates a relationship where an entity’s primary or defining movement action or motion pattern is specified or referenced.
-
D.
movement3Key
Indicates a three-part or third-level categorization of how an entity moves or changes location relative to another entity or reference point.
-
E.
thirdMovementKey
Indicates the musical key in which the third movement of a multi-movement work is composed or performed.
- 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_69ca832b56948190ba751cec255308f1 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46da609881909a6d851915e8df14 |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:24 p.m.