Triple
T31613141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto No. 4 in D minor, Op. 70 |
E806679
|
entity |
| Predicate | hasOrchestralRole |
P114150
|
FINISHED |
| Object | symphonic partner to 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: symphonic partner to soloist | Statement: [Piano Concerto No. 4 in D minor, Op. 70, hasOrchestralRole, symphonic partner to soloist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrchestralRole Context triple: [Piano Concerto No. 4 in D minor, Op. 70, hasOrchestralRole, symphonic partner to soloist]
-
A.
orchestralRole
chosen
Indicates the specific function or position an entity holds within an orchestra (e.g., conductor, principal violin, section player).
-
B.
performedWithOrchestra
Indicates that a performance or musical work was carried out in collaboration with an orchestra.
-
C.
isOrchestralWorkBy
Indicates that a particular orchestral work was created or composed by a specified composer or artist.
-
D.
hasOrchestraType
Indicates that an entity is associated with, or classified by, a specific type or category of orchestra.
-
E.
isOrchestral
Indicates that something involves, is written for, or is performed by an orchestra.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 30, 2026, 10:37 p.m.