Triple

T15166648
Position Surface form Disambiguated ID Type / Status
Subject Hypersleep E362364 entity
Predicate hasOriginGenreScene P22737 FINISHED
Object American noise rock scene 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: American noise rock scene | Statement: [Hypersleep, hasOriginGenreScene, American noise rock scene]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOriginGenreScene
Context triple: [Hypersleep, hasOriginGenreScene, American noise rock scene]
  • A. associatedWithGenreScene chosen
    Indicates that an entity is connected or related to a particular genre scene, such as a specific stylistic or cultural subcommunity within a broader genre.
  • B. hasGenreOrigin
    Indicates that a genre originates from, or has its roots in, a particular source, place, culture, or tradition.
  • C. hasGenreScope
    Indicates that something (such as a work, collection, or classification) is limited to, defined by, or applicable within a particular genre or set of genres.
  • D. parentGenreScene
    Indicates that one scene genre functions as the parent or broader category of another scene genre.
  • E. hasStageGenre
    Indicates a relationship where a stage production or performance is associated with a particular theatrical or performance genre.
  • 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_69d85a087b7c81908baa94a53dac8d68 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0064c6244819085daf8e1eafdf3f2 completed April 15, 2026, 9:42 p.m.
PD Predicate disambiguation batch_69deb9779acc81908ed2dad382c42dca completed April 14, 2026, 10:02 p.m.
Created at: April 10, 2026, 3:08 a.m.