Triple
T20419533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | At the Crescendo |
E500809
|
entity |
| Predicate | featuresGenreStyle |
P120127
|
FINISHED |
| Object | traditional jazz |
—
|
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: traditional jazz | Statement: [At the Crescendo, featuresGenreStyle, traditional jazz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresGenreStyle Context triple: [At the Crescendo, featuresGenreStyle, traditional jazz]
-
A.
genreFeatures
Indicates that a particular genre is characterized or defined by certain features or attributes.
-
B.
styleOfMusic
Indicates the musical genre or stylistic category that characterizes a piece of music, artist, or performance.
-
C.
genreFunction
Indicates the role or purpose that a genre serves in relation to an entity, such as how it functions within classification, interpretation, or use.
-
D.
hasGenreFeature
chosen
Indicates that something possesses a characteristic, element, or trait associated with a particular genre.
-
E.
musicBrainzGenre
Indicates that one entity is associated with a musical genre classification as defined in the MusicBrainz database.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67ba39f7081909358f1103a0f241c |
completed | April 20, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.