Triple
T14623189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time of My Life |
E343274
|
entity |
| Predicate | mainGenreDescription |
P51264
|
FINISHED |
| Object | polished post-grunge sound and radio-friendly anthems |
—
|
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: polished post-grunge sound and radio-friendly anthems | Statement: [Time of My Life, mainGenreDescription, polished post-grunge sound and radio-friendly anthems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainGenreDescription Context triple: [Time of My Life, mainGenreDescription, polished post-grunge sound and radio-friendly anthems]
-
A.
commonGenre
Indicates that two entities share at least one genre in common.
-
B.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
C.
hasMainGenre
chosen
Indicates that an entity’s primary or most characteristic genre is the specified genre.
-
D.
genreFeatures
Indicates that a particular genre is characterized or defined by certain features or attributes.
-
E.
usedGenre
Indicates that one entity employs or is associated with a particular genre in its creation, presentation, or classification.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb468acc4819083b7e818d5cec809 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:26 a.m.