Triple
T38200665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hole in My Soul |
E1009044
|
entity |
| Predicate | hasBPMApproximate |
P22758
|
FINISHED |
| Object | slow-to-mid tempo |
—
|
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: slow-to-mid tempo | Statement: [Hole in My Soul, hasBPMApproximate, slow-to-mid tempo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBPMApproximate Context triple: [Hole in My Soul, hasBPMApproximate, slow-to-mid tempo]
-
A.
hasBPMApprox
chosen
Indicates an approximate beats-per-minute (BPM) value associated with an entity, rather than an exact measured tempo.
-
B.
hasBPMStatus
Indicates that an entity has a specific status or state within a business process management (BPM) workflow.
-
C.
hasTempoChanges
Indicates that the tempo of the piece or segment changes over its duration, rather than remaining constant.
-
D.
hasNotableBeat
Indicates that an entity (such as a journalist or reporter) is professionally assigned to cover a specific topic, area, or subject as their primary reporting focus.
-
E.
hasBeat
Indicates that one entity has defeated or surpassed another in a competitive or comparative context.
- 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.