Triple
T29227815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirty Little Girl |
E740980
|
entity |
| Predicate | hasCoverArtForRelease |
P159880
|
FINISHED |
| Object | Goodbye Yellow Brick Road album cover |
—
|
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: Goodbye Yellow Brick Road album cover | Statement: [Dirty Little Girl, hasCoverArtForRelease, Goodbye Yellow Brick Road album cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverArtForRelease Context triple: [Dirty Little Girl, hasCoverArtForRelease, Goodbye Yellow Brick Road album cover]
-
A.
hasCoverArtSource
Indicates that an entity’s cover art is derived from, or visually based on, another specified source entity.
-
B.
hasCoverArtFeaturing
Indicates that one entity’s cover art visually features or depicts another entity.
-
C.
hasCoverArtVariant
Indicates that an item has an alternative version of its cover artwork distinct from the primary cover.
-
D.
isCoverArtFor
chosen
Indicates that one item serves as the cover artwork or visual representation for another item, such as a publication, recording, or product.
-
E.
hasCoverArtIssue
Indicates that there is a problem, defect, or inconsistency associated with the cover art of an item.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a005247dba08190acadf962bcefe4a0 |
completed | May 10, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_6a00519029848190a234358dfba45084 |
completed | May 10, 2026, 9:36 a.m. |
Created at: April 28, 2026, 12:17 p.m.