Triple
T37359471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mozart K. 622 |
E927539
|
entity |
| Predicate | standardSoloInstrumentVersion |
P12878
|
FINISHED |
| Object | A clarinet |
—
|
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: A clarinet | Statement: [Mozart K. 622, standardSoloInstrumentVersion, A clarinet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardSoloInstrumentVersion Context triple: [Mozart K. 622, standardSoloInstrumentVersion, A clarinet]
-
A.
frequentSoloInstrument
Indicates that an instrument is commonly used as a solo instrument in performances or compositions.
-
B.
traditionalInstrument
Indicates that an entity is a musical instrument associated with the traditional or customary music of a particular culture, region, or community.
-
C.
arrangedSoloInstrument
Indicates that a musical work has been arranged specifically for performance by a single solo instrument.
-
D.
instrumentalSoloist
Indicates that an entity performs a featured solo part on a musical instrument within a work or performance.
-
E.
musicInstrumentation
chosen
Indicates the specific instruments or instrumental forces used to perform a piece of music.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 3, 2026, 4:16 p.m.