Triple
T18504332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoop |
E452160
|
entity |
| Predicate | hasBpmRange |
P22758
|
FINISHED |
| Object | 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: mid-tempo | Statement: [Shoop, hasBpmRange, mid-tempo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBpmRange Context triple: [Shoop, hasBpmRange, mid-tempo]
-
A.
hasBPMApprox
chosen
Indicates an approximate beats-per-minute (BPM) value associated with an entity, rather than an exact measured tempo.
-
B.
hasBandRange
Indicates that one entity has an associated range or span of bands (such as frequency or wavelength intervals) defined by the other entity.
-
C.
hasTempoChanges
Indicates that the tempo of the piece or segment changes over its duration, rather than remaining constant.
-
D.
hasBWVRangeContext
Indicates that a relationship or action is situated within, or constrained by, a specific range of BWV (Bach-Werke-Verzeichnis) catalogue numbers.
-
E.
hasTempoVariety
Indicates that an entity exhibits variation or changes in tempo rather than maintaining a constant speed.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53341063c81908361b0eb78794145 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.