Triple
T17439036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Get Your Shine On |
E424098
|
entity |
| Predicate | featuresCountryRockElements |
P127456
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Get Your Shine On, featuresCountryRockElements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresCountryRockElements Context triple: [Get Your Shine On, featuresCountryRockElements, true]
-
A.
hasRockSubgenre
Indicates a relationship where one musical style is classified as a subgenre within the broader category of rock music.
-
B.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
C.
usesWorldMusicElements
Indicates that something incorporates stylistic, rhythmic, melodic, or instrumental features associated with musical traditions from various cultures around the world.
-
D.
featuresRhythm
Indicates that something includes, exhibits, or is characterized by a particular rhythmic pattern or structure.
-
E.
featuresFictionalBand
Indicates that something (such as a work or event) includes or presents a fictional band as part of its content or narrative.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ff584cc81908207c163f19ff972 |
completed | April 19, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:46 a.m.