Triple
T11649665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romantic Piano Concerto series |
E276867
|
entity |
| Predicate | musicalPeriodCovered |
P38929
|
FINISHED |
| Object | Romantic era |
—
|
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: Romantic era | Statement: [Romantic Piano Concerto series, musicalPeriodCovered, Romantic era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalPeriodCovered Context triple: [Romantic Piano Concerto series, musicalPeriodCovered, Romantic era]
-
A.
musicalEra
chosen
Indicates the historical musical period or style with which an entity (such as a composition, performance, or musician) is associated.
-
B.
hasGenrePeriod
Indicates a relationship where an entity is associated with a specific historical or stylistic period that characterizes its genre.
-
C.
musicalTheatreEra
Indicates the historical period or stylistic era of musical theatre with which an entity is associated.
-
D.
recordingEra
Indicates the historical time period or era during which the recording was made.
-
E.
timePeriodOfMusic
Indicates the historical or stylistic time period during which a piece of music was created, popular, or characteristic.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cea9308190a13f7dd995ea07a4 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.