Triple
T5696753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosetta |
E125557
|
entity |
| Predicate | hasMelodicRole |
P41587
|
FINISHED |
| Object | improvisation vehicle for jazz soloists |
—
|
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: improvisation vehicle for jazz soloists | Statement: [Rosetta, hasMelodicRole, improvisation vehicle for jazz soloists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMelodicRole Context triple: [Rosetta, hasMelodicRole, improvisation vehicle for jazz soloists]
-
A.
hasMelody
Indicates that one entity possesses, contains, or is characterized by a particular melody.
-
B.
melodyType
Indicates the specific kind or category of melody associated with or used by an entity.
-
C.
musicalFunction
chosen
Indicates the specific role or function an entity plays within a musical context, such as its harmonic, structural, or performative purpose in a piece or performance.
-
D.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
E.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:45 p.m.