Triple
T37611651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brahms violin sonatas |
E935798
|
entity |
| Predicate | secondSonata |
P200657
|
FINISHED |
| Object | Violin Sonata No. 2 in A major, Op. 100 |
—
|
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: Violin Sonata No. 2 in A major, Op. 100 | Statement: [Brahms violin sonatas, secondSonata, Violin Sonata No. 2 in A major, Op. 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondSonata Context triple: [Brahms violin sonatas, secondSonata, Violin Sonata No. 2 in A major, Op. 100]
-
A.
keyOfSecondSonata
Indicates the musical key in which the second sonata of a given work or composer is written.
-
B.
thirdSonata
Indicates that one entity is the third sonata composed, owned, or otherwise associated within a series or set related to another entity.
-
C.
secondSymphonyComposed
Indicates that an entity composed the second symphony associated with another entity (typically a composer and their second symphonic work).
-
D.
movementCountSecondSonata
Indicates the number of movements contained in a musical work identified as the second sonata.
-
E.
sonataNumber
Indicates the specific numbered position of a sonata within a composer's or collection's sequence of sonatas.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69ff9d9ba1ac8190a0cca5764bb5904d |
completed | May 9, 2026, 8:48 p.m. |
Created at: May 3, 2026, 4:18 p.m.