Triple
T29530075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oboe Concerto |
E749173
|
entity |
| Predicate | intendedSoloist |
P69077
|
FINISHED |
| Object | oboe soloist |
—
|
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: oboe soloist | Statement: [Oboe Concerto, intendedSoloist, oboe soloist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedSoloist Context triple: [Oboe Concerto, intendedSoloist, oboe soloist]
-
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.
isSoloPerformance
Indicates that the performance is carried out by a single performer without accompaniment or participation from others.
-
D.
instrumentalSoloist
chosen
Indicates that an entity performs a featured solo part on a musical instrument within a work or performance.
-
E.
hasImprovisedSoloBy
Indicates that an improvised solo performance is attributed to or performed by a specific entity.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 28, 2026, 4:51 p.m.