Triple
T3086962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Master Blaster (Jammin') |
E64393
|
entity |
| Predicate | hasRhythmicInfluence |
P22766
|
FINISHED |
| Object | reggae |
—
|
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: reggae | Statement: [Master Blaster (Jammin'), hasRhythmicInfluence, reggae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRhythmicInfluence Context triple: [Master Blaster (Jammin'), hasRhythmicInfluence, reggae]
-
A.
hasRhythmicStyle
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
-
B.
hasGenreInfluenceOn
chosen
Indicates that one genre has a notable impact on shaping or influencing the characteristics, style, or development of another genre.
-
C.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
D.
hasRitualMusic
Indicates that one entity is associated with or characterized by ritual music used in formal or ceremonial practices.
-
E.
hasMusicalForm
Indicates that one entity (typically a musical work or piece) is characterized by or structured according to a particular musical form.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1ec187c819084565514ebb99cdb |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.