Triple
T21762966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto No. 1 |
E537206
|
entity |
| Predicate | premiereTrumpeter |
P32661
|
FINISHED |
| Object | Alexander Schmidt |
—
|
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: Alexander Schmidt | Statement: [Piano Concerto No. 1, premiereTrumpeter, Alexander Schmidt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiereTrumpeter Context triple: [Piano Concerto No. 1, premiereTrumpeter, Alexander Schmidt]
-
A.
trumpeter
Indicates that an entity plays the trumpet, typically as their role, profession, or primary musical activity in relation to another context or entity.
-
B.
hasPrincipalTrumpet
Indicates that one entity serves as the principal (lead) trumpet player for another entity, such as an orchestra or ensemble.
-
C.
premiereSoloist
chosen
Indicates that an entity serves as the primary featured solo performer in a particular performance or production.
-
D.
premiereEdition
Indicates that an entity is the first or original edition in which a work was initially released or premiered.
-
E.
hasPremier
Indicates that an entity has a specific individual serving as its premier (head of government).
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031a711dc8190a786c9849dc344e8 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.