Triple
T26146877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concerto for Clarinet |
E659693
|
entity |
| Predicate | primarySoloInstrument |
P146520
|
FINISHED |
| Object | 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: clarinet | Statement: [Concerto for Clarinet, primarySoloInstrument, clarinet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySoloInstrument Context triple: [Concerto for Clarinet, primarySoloInstrument, clarinet]
-
A.
primaryInstrumentAbbreviation
Indicates that one entity is the standard shortened or abbreviated form of the name of another entity’s primary instrument.
-
B.
primaryInstrumentFamily
Indicates the main family or category of musical instruments with which an entity is primarily associated.
-
C.
primaryInstrumentalStyle
Indicates the main instrumental style or genre most closely associated with an entity’s musical performance or work.
-
D.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
E.
frequentSoloInstrument
chosen
Indicates that an instrument is commonly used as a solo instrument in performances or compositions.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: April 26, 2026, 8:23 p.m.