Triple
T37611173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violin Concerto in D major, Op. 77 |
E935786
|
entity |
| Predicate | onlyViolinConcertoBy |
P188755
|
FINISHED |
| Object | Johannes Brahms |
—
|
NE NERFINISHED |
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: Johannes Brahms | Statement: [Violin Concerto in D major, Op. 77, onlyViolinConcertoBy, Johannes Brahms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onlyViolinConcertoBy Context triple: [Violin Concerto in D major, Op. 77, onlyViolinConcertoBy, Johannes Brahms]
-
A.
isMostFrequentlyPerformedViolinSonataBy
Indicates that the subject is the violin sonata most often performed by the specified agent or performer.
-
B.
principalViolin
Indicates that an entity serves as the lead or primary violin in a musical ensemble or context.
-
C.
hasViolinist
Indicates that an entity is associated with or includes a violinist as part of its composition, membership, or participants.
-
D.
instrumentalSoloist
Indicates that an entity performs a featured solo part on a musical instrument within a work or performance.
-
E.
soloist
Indicates that an entity performs or appears alone as the primary featured performer in an artistic or musical context.
- F. None of above. chosen
Provenance (4 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:18 p.m.