Triple
T32863112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Improvisation 21 |
E840571
|
entity |
| Predicate | languageOfMusicalStyle |
P201439
|
FINISHED |
| Object | Hungarian modernism |
—
|
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: Hungarian modernism | Statement: [Improvisation 21, languageOfMusicalStyle, Hungarian modernism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfMusicalStyle Context triple: [Improvisation 21, languageOfMusicalStyle, Hungarian modernism]
-
A.
languageOfMusic
Indicates that a specified language is used in, associated with, or characteristic of a particular piece of music or musical work.
-
B.
languageOfMusicalTerms
Indicates the language in which specific musical terms are expressed or defined.
-
C.
styleOfMusic
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
-
D.
musicalStyleRequirement
Indicates that a specific musical style is required or prescribed for a given entity, context, or performance.
-
E.
includesMusicalStyle
Indicates that one entity encompasses, features, or incorporates a particular musical style as part of its content or character.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fff59a00a881909b35b799654b3c45 |
completed | May 10, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69fff4d0a2e081909c972189b33d0128 |
completed | May 10, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69fff59875cc8190864864e951951679 |
completed | May 10, 2026, 3:03 a.m. |
Created at: May 1, 2026, 1:17 a.m.