Triple
T38657263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K. 467 |
E939924
|
entity |
| Predicate | secondMovementNickname |
P201358
|
FINISHED |
| Object | Elvira Madigan |
—
|
NE NERFINISHED |
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: Elvira Madigan | Statement: [K. 467, secondMovementNickname, Elvira Madigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondMovementNickname Context triple: [K. 467, secondMovementNickname, Elvira Madigan]
-
A.
secondMovementTitle
Indicates the title or name given to the second movement of a multi-movement musical work.
-
B.
secondMovementCharacter
Indicates the characteristic or quality that defines the second movement of a multi-movement work.
-
C.
secondMovementForm
Indicates that an entity is in the form or structure of the second movement within a larger multi-movement work or sequence.
-
D.
secondMovementKey
Indicates the musical key in which the second movement of a multi-movement work is composed.
-
E.
secondMovementFeature
Indicates that the subject is characterized by or associated with a specific feature of the second movement within a larger sequence or structure.
- F. None of above. chosen
Provenance (4 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffecdcbac4819093b725a7dbe0e61b |
completed | May 10, 2026, 2:26 a.m. |
| PD | Predicate disambiguation | batch_69ffec3633288190adbbd84e277708dc |
completed | May 10, 2026, 2:23 a.m. |
| PDg | Predicate description generation | batch_69ffecdbe62081909f901e7d4db69d60 |
completed | May 10, 2026, 2:26 a.m. |
Created at: May 3, 2026, 4:33 p.m.