Triple
T24254819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Demon |
E603638
|
entity |
| Predicate | associatedGenreAesthetic |
P102534
|
FINISHED |
| Object | shock rock |
—
|
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: shock rock | Statement: [The Demon, associatedGenreAesthetic, shock rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedGenreAesthetic Context triple: [The Demon, associatedGenreAesthetic, shock rock]
-
A.
associatedAesthetic
chosen
Indicates a relationship where one entity is linked to or characterized by a particular aesthetic style, quality, or visual/theme-based sensibility.
-
B.
genreAssociatedWith
Indicates a relationship where a work, item, or entity is linked to or categorized under a particular genre.
-
C.
hasGenreInfluenceOn
Indicates that one genre has a notable impact on shaping or influencing the characteristics, style, or development of another genre.
-
D.
genreOfAssociatedPerson
Indicates that a particular genre is associated with a given person, such as an artist, author, or performer.
-
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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b8ca4988190b565c2873dc6559d |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:05 a.m.