Triple
T36780179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern soul |
E908745
|
entity |
| Predicate | typicalBPM |
—
|
GENERATED |
| Object | 100–140 BPM |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBPM Context triple: [Northern soul, typicalBPM, 100–140 BPM]
-
A.
typicalBeatCount
Indicates the usual or standard number of beats associated with an event, pattern, or unit (such as a musical measure or rhythmic figure).
-
B.
typicalTempoPattern
Indicates the characteristic or commonly occurring tempo progression or rhythmic pattern associated with an action or event.
-
C.
typicalBeatPattern
Indicates the characteristic or standard rhythmic pattern that usually occurs in a given musical or temporal context.
-
D.
typicalTempoCharacterization
chosen
Indicates how the usual or characteristic tempo of something is described or classified.
-
E.
typicalTempoControl
Indicates that one entity serves as the usual or standard means by which the tempo of another entity (such as a process or activity) is regulated or controlled.
- F. None of above.
Provenance (1 batch)
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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.