Triple
T32362439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saxophone Concerto in E-flat major, Op. 109 |
E826899
|
entity |
| Predicate | originalSoloist |
P11499
|
FINISHED |
| Object | Sigurd Raschèr |
E2004852
|
NE 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: Sigurd Raschèr | Statement: [Saxophone Concerto in E-flat major, Op. 109, originalSoloist, Sigurd Raschèr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalSoloist Context triple: [Saxophone Concerto in E-flat major, Op. 109, originalSoloist, Sigurd Raschèr]
-
A.
soloist
Indicates that an entity performs or appears alone as the primary featured performer in an artistic or musical context.
-
B.
soloistRole
Indicates that an entity has the role of performing as a soloist within a work, event, or performance.
-
C.
isSoloDebutOf
Indicates that an event, work, or performance is the first solo appearance or release of a particular individual.
-
D.
originalPerformer
chosen
Indicates that an entity is the first or initial performer of a work, role, or performance.
-
E.
madeArtistASoloStar
Indicates that one entity was responsible for establishing another artist as a solo star, distinct from any group or collaborative identity.
- F. None of above.
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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01a18e350481909f848686568d19bc |
completed | May 11, 2026, 9:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34666756e88190b64e357ef9dbc6bf |
completed | June 18, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_6a01a121b67c81908a6c5be9eb8e9ca5 |
completed | May 11, 2026, 9:28 a.m. |
Created at: May 1, 2026, 12:49 a.m.