Triple
T7603600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double Concerto for Double Bass and Cello |
E180044
|
entity |
| Predicate | coSoloistInstrument |
P13954
|
FINISHED |
| Object | double bass |
—
|
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: double bass | Statement: [Double Concerto for Double Bass and Cello, coSoloistInstrument, double bass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coSoloistInstrument Context triple: [Double Concerto for Double Bass and Cello, coSoloistInstrument, double bass]
-
A.
instrumentalSoloist
Indicates that an entity performs a featured solo part on a musical instrument within a work or performance.
-
B.
hasImprovisedSoloBy
Indicates that an improvised solo performance is attributed to or performed by a specific entity.
-
C.
coInstrumentWith
chosen
Indicates that two or more entities are used together as instruments or means to perform the same action or achieve the same outcome.
-
D.
typeOfInstrument
Indicates the specific kind or category of instrument associated with an entity.
-
E.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
- 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9fa633081909660f653f5b073cd |
completed | March 27, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:54 p.m.