Triple
T5031027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruckner symphony cycle with the Gewandhausorchester Leipzig |
E113301
|
entity |
| Predicate | periodOfMusic |
P38929
|
FINISHED |
| Object | 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: Romantic | Statement: [Bruckner symphony cycle with the Gewandhausorchester Leipzig, periodOfMusic, Romantic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfMusic Context triple: [Bruckner symphony cycle with the Gewandhausorchester Leipzig, periodOfMusic, Romantic]
-
A.
timePeriodOfMusic
Indicates the historical or stylistic time period during which a piece of music was created, popular, or characteristic.
-
B.
musicalEra
chosen
Indicates the historical musical period or style with which an entity (such as a composition, performance, or musician) is associated.
-
C.
styleOfMusic
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
-
D.
recordingEra
Indicates the historical time period or era during which the recording was made.
-
E.
partOfMusical
Indicates that something is a component, segment, or element belonging to a larger musical work or performance.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73922a4c81908651c2d9b5e01cb6 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.