Triple
T37611437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarinet Sonatas, Op. 120 |
E935793
|
entity |
| Predicate | secondWorkTitle |
P17199
|
FINISHED |
| Object | Sonata for Clarinet and Piano in E-flat major, Op. 120 No. 2 |
—
|
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: Sonata for Clarinet and Piano in E-flat major, Op. 120 No. 2 | Statement: [Clarinet Sonatas, Op. 120, secondWorkTitle, Sonata for Clarinet and Piano in E-flat major, Op. 120 No. 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondWorkTitle Context triple: [Clarinet Sonatas, Op. 120, secondWorkTitle, Sonata for Clarinet and Piano in E-flat major, Op. 120 No. 2]
-
A.
secondWork
chosen
Indicates that one work is the second in order relative to another work within a sequence or set.
-
B.
secondPartTitle
Indicates that one entity is the second part of the title of another entity.
-
C.
secondSeriesTitle
Indicates that an entity has a second series whose title is given by the related value.
-
D.
secondShortTitle
Indicates that an entity has a secondary or alternative short title associated with it.
-
E.
secondMovementTitle
Indicates the title or name given to the second movement of a multi-movement musical work.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:18 p.m.