Triple
T28416921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto No. 2 in F minor |
E719831
|
entity |
| Predicate | premiereRoleOfPerformer |
P169278
|
FINISHED |
| Object | piano 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: piano soloist | Statement: [Piano Concerto No. 2 in F minor, premiereRoleOfPerformer, piano soloist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiereRoleOfPerformer Context triple: [Piano Concerto No. 2 in F minor, premiereRoleOfPerformer, piano soloist]
-
A.
performerOfPremiere
Indicates that an entity is the performer who gave the first (premiere) performance of a work or event.
-
B.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
-
C.
premieredWorkBy
Indicates that a creative work had its first public performance, showing, or presentation conducted by the specified entity.
-
D.
originalLeadActorRole
Indicates the role originally played by a particular lead actor in a given production or work.
-
E.
entertainmentRole
Indicates that an entity holds a specific function or position within an entertainment context (such as a role in a performance, production, or media work).
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 28, 2026, 1:31 a.m.