Triple
T27046868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playlist For An Extreme Occasion |
E684659
|
entity |
| Predicate | mayIncludeGenre |
P55821
|
FINISHED |
| Object | dubstep |
—
|
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: dubstep | Statement: [Playlist For An Extreme Occasion, mayIncludeGenre, dubstep]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayIncludeGenre Context triple: [Playlist For An Extreme Occasion, mayIncludeGenre, dubstep]
-
A.
genreIncludes
Indicates that a broader genre category encompasses or contains a specified subgenre or work as part of its classification.
-
B.
supportedGenre
Indicates that an entity (such as a system, service, or tool) is capable of handling, providing, or working with a specified genre.
-
C.
typicalGenresIncluded
chosen
Indicates that certain genres are commonly or characteristically included as part of another entity’s usual set of genres.
-
D.
hasGenreEligibility
Indicates that an entity qualifies to be categorized under a particular genre according to defined criteria.
-
E.
hasTargetGenreCategory
Indicates that something is associated with or classified under a specific target genre category.
- 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_69ef148193c48190bb1a0cfae6a407c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 8:11 a.m.