Triple
T25246480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life |
E632619
|
entity |
| Predicate | timeSincePreviousStudioAlbum |
P122791
|
FINISHED |
| Object | 19 years |
—
|
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: 19 years | Statement: [Life, timeSincePreviousStudioAlbum, 19 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSincePreviousStudioAlbum Context triple: [Life, timeSincePreviousStudioAlbum, 19 years]
-
A.
hiatusSincePreviousAlbum
chosen
Indicates the length of time that has passed between the release of the previous album and the current one.
-
B.
yearsSincePreviousSoloSingle
Indicates the number of years that have passed between an entity’s current solo single and their immediately preceding solo single.
-
C.
isFirstSoloAlbumInYearsFor
Indicates that an album is the first solo release an artist has put out after a significant multi-year gap since their previous solo album.
-
D.
hasNoStudioAlbums
Indicates that the subject entity does not have any studio albums associated with it.
-
E.
timeInArtistCareer
Indicates the point or period within an artist’s professional career at which a given event, work, or activity occurs.
- 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48086e9088190b8a78f3665a7a25b |
completed | May 1, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:10 p.m.