Triple
T11475869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarinet Concerto in A major |
E272022
|
entity |
| Predicate | typicalSoloist |
P69077
|
FINISHED |
| Object | classical clarinetist |
—
|
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: classical clarinetist | Statement: [Clarinet Concerto in A major, typicalSoloist, classical clarinetist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSoloist Context triple: [Clarinet Concerto in A major, typicalSoloist, classical clarinetist]
-
A.
soloist
Indicates that an entity performs or appears alone as the primary featured performer in an artistic or musical context.
-
B.
numberOfSoloists
Indicates the quantity of individual performers who play or sing solo parts within a given musical work, performance, or section.
-
C.
instrumentalSoloist
chosen
Indicates that an entity performs a featured solo part on a musical instrument within a work or performance.
-
D.
typicalPerformance
Indicates the usual or characteristic level at which an entity performs under normal conditions.
-
E.
typicalPerformerRoleType
Indicates the usual or characteristic role type that a performer commonly plays or is associated with in their performances.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294c8dc48190a515f83c99405a3b |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.