Triple
T31912350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Good Year for the Roses |
E814720
|
entity |
| Predicate | notableCoverYear |
P93128
|
FINISHED |
| Object | 1981 |
—
|
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: 1981 | Statement: [A Good Year for the Roses, notableCoverYear, 1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCoverYear Context triple: [A Good Year for the Roses, notableCoverYear, 1981]
-
A.
notableCoverReleaseYear
chosen
Indicates the year in which a particularly notable or significant cover version of a work was released.
-
B.
notableCoverAlbum
Indicates that one entity is a notable album consisting primarily of cover versions of songs originally by another entity.
-
C.
notableCover
Indicates that one entity is a particularly well-known or significant cover version or adaptation of another entity.
-
D.
notableEditionYear
Indicates the year in which a particular edition of something (such as a work, product, or publication) is considered notable or significant.
-
E.
decadeOfNotableCover
Indicates the decade during which a notable cover version of a work was released or became prominent.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:01 a.m.