Triple
T20417430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jhankaar Beats |
E500748
|
entity |
| Predicate | soundtrackPopularity |
P140066
|
FINISHED |
| Object | cult following |
—
|
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: cult following | Statement: [Jhankaar Beats, soundtrackPopularity, cult following]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundtrackPopularity Context triple: [Jhankaar Beats, soundtrackPopularity, cult following]
-
A.
soundtrackRelease
Indicates that a soundtrack has been officially released, typically as a published audio recording associated with another work.
-
B.
peakPopularity
Indicates the time or context in which something reaches its highest level of popularity relative to other times or contexts.
-
C.
soundtrackFeatures
Indicates that a particular soundtrack includes or showcases a given piece of music, artist, or audio element as part of its content.
-
D.
isSoundtrackOf
Indicates that a piece of music or collection of music serves as the soundtrack for a particular work, such as a film, game, or show.
-
E.
soundtrackType
Indicates the specific category or format of a soundtrack associated with a work, such as score, compilation, or original soundtrack.
- F. None of above. chosen
Provenance (4 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a44ecf48190ba5a3872af500dc8 |
completed | April 20, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
| PDg | Predicate description generation | batch_69e58d766b408190a1d3698145fb6d30 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:30 a.m.