Triple
T11677009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto No. 2 in B-flat major, Op. 83 |
E277517
|
entity |
| Predicate | associatedMusicalEra |
P38929
|
FINISHED |
| Object | late Romantic |
—
|
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: late Romantic | Statement: [Piano Concerto No. 2 in B-flat major, Op. 83, associatedMusicalEra, late Romantic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMusicalEra Context triple: [Piano Concerto No. 2 in B-flat major, Op. 83, associatedMusicalEra, late Romantic]
-
A.
musicalEra
chosen
Indicates the historical musical period or style with which an entity (such as a composition, performance, or musician) is associated.
-
B.
associatedWithArtistEra
Indicates a relationship where an artist is linked to a particular artistic era or period with which their work or influence is identified.
-
C.
recordingEra
Indicates the historical time period or era during which the recording was made.
-
D.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
E.
musicalTheatreEra
Indicates the historical period or stylistic era of musical theatre with which an entity is associated.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a46000a48190888ad1a6ade052e3 |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.