Triple
T24980554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadder Than Blue |
E625150
|
entity |
| Predicate | hasMusicalArtistCharacteristic |
P160081
|
FINISHED |
| Object | emotional ballad style |
—
|
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: emotional ballad style | Statement: [Sadder Than Blue, hasMusicalArtistCharacteristic, emotional ballad style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalArtistCharacteristic Context triple: [Sadder Than Blue, hasMusicalArtistCharacteristic, emotional ballad style]
-
A.
hasMusicalArtistCharacteristic
chosen
Indicates that a musical artist possesses a particular characteristic, quality, or attribute.
-
B.
hasMusicalArtistType
Indicates that an entity has a specific role or classification as a type of musical artist (e.g., solo artist, band, composer).
-
C.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
-
D.
hasMusicalArtistOccupation
Indicates that an entity has an occupation or professional role as a musical artist.
-
E.
hasMusicalWorkType
Indicates that a musical work is associated with a specific type or category of musical composition.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 6:02 a.m.