Triple
T29539368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Tribe |
E749447
|
entity |
| Predicate | typicalBPMRange |
P148387
|
FINISHED |
| Object | high-tempo psytrance |
—
|
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: high-tempo psytrance | Statement: [Space Tribe, typicalBPMRange, high-tempo psytrance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBPMRange Context triple: [Space Tribe, typicalBPMRange, high-tempo psytrance]
-
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.
hasBPMApprox
Indicates an approximate beats-per-minute (BPM) value associated with an entity, rather than an exact measured tempo.
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a01d48f41f4819093a5b47288a073c1 |
completed | May 11, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_6a01d3fa278c8190838174dd96ef5dde |
completed | May 11, 2026, 1:04 p.m. |
Created at: April 28, 2026, 5:01 p.m.