Triple
T28960185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resistance Stage |
E731873
|
entity |
| Predicate | musicTempoRange |
P140820
|
FINISHED |
| Object | typically between 120 and 130 BPM |
—
|
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: typically between 120 and 130 BPM | Statement: [Resistance Stage, musicTempoRange, typically between 120 and 130 BPM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicTempoRange Context triple: [Resistance Stage, musicTempoRange, typically between 120 and 130 BPM]
-
A.
musicalTempo
chosen
Indicates the speed or pace at which a piece of music is performed or intended to be performed.
-
B.
movement7Tempo
Indicates the tempo at which the seventh movement of a work is performed or intended to be played.
-
C.
movement6Tempo
Indicates the tempo or speed at which the sixth movement of a work is performed or proceeds.
-
D.
commonTempo
Indicates that two or more musical entities share the same tempo or rate of beats per minute.
-
E.
hasTempoChanges
Indicates that the tempo of the piece or segment changes over its duration, rather than remaining constant.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 28, 2026, 8:50 a.m.