Triple
T15167667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You Can't Beat Tomorrow |
E362395
|
entity |
| Predicate | hasMusicalStyleOfArtist |
P22764
|
FINISHED |
| Object | experimental rock |
—
|
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: experimental rock | Statement: [You Can't Beat Tomorrow, hasMusicalStyleOfArtist, experimental rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalStyleOfArtist Context triple: [You Can't Beat Tomorrow, hasMusicalStyleOfArtist, experimental rock]
-
A.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
-
B.
hasMusicalStyleSimilarTo
Indicates that two entities share a comparable or closely related musical style or sound.
-
C.
hasMusicalArtistType
Indicates that an entity has a specific role or classification as a type of musical artist (e.g., solo artist, band, composer).
-
D.
includesMusicalStyle
chosen
Indicates that one entity encompasses, features, or incorporates a particular musical style as part of its content or character.
-
E.
hasSongStyle
Indicates that an entity possesses, is characterized by, or is associated with a particular style or genre of song.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0064dba588190a4341775b472a6d3 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:08 a.m.