Triple
T15653286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busy Signal |
E376364
|
entity |
| Predicate | originGenreScene |
P22737
|
FINISHED |
| Object | Kingston dancehall 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: Kingston dancehall scene | Statement: [Busy Signal, originGenreScene, Kingston dancehall scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originGenreScene Context triple: [Busy Signal, originGenreScene, Kingston dancehall scene]
-
A.
parentGenreScene
Indicates that one scene genre functions as the parent or broader category of another scene genre.
-
B.
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.
-
C.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
D.
primarySourceGenre
Indicates the genre or type of creative work that serves as the primary source for something (e.g., an adaptation, derivative work, or related resource).
-
E.
hasGenreOrigin
Indicates that a genre originates from, or has its roots in, a particular source, place, culture, or tradition.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef089948190902ec22f4d7bc932 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.