Triple
T19358577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Back Pages |
E484215
|
entity |
| Predicate | notableCoverGenre |
P135227
|
FINISHED |
| Object | folk 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: folk rock | Statement: [My Back Pages, notableCoverGenre, folk rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCoverGenre Context triple: [My Back Pages, notableCoverGenre, folk rock]
-
A.
notableCover
Indicates that one entity is a particularly well-known or significant cover version or adaptation of another entity.
-
B.
notableCoverAlbum
Indicates that one entity is a notable album consisting primarily of cover versions of songs originally by another entity.
-
C.
notableCoverReleaseYear
Indicates the year in which a particularly notable or significant cover version of a work was released.
-
D.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
E.
liveCoverNotableBy
Indicates that a live performance of a work is notably covered or performed by a particular artist or entity.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6190a1ec88190ba6d2d45174dc85a |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd13a8cc81909cd02668564c9f29 |
completed | April 19, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69e4dde92ff481909006b3f9e8d639d4 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:34 p.m.