Triple
T31889390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelter (Violin Mix) |
E814101
|
entity |
| Predicate | hasTempoType |
P83539
|
FINISHED |
| Object | moderate |
—
|
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: moderate | Statement: [Shelter (Violin Mix), hasTempoType, moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTempoType Context triple: [Shelter (Violin Mix), hasTempoType, moderate]
-
A.
hasTempoCategory
chosen
Indicates that something is associated with a particular tempo classification or speed category.
-
B.
hasTempoChanges
Indicates that the tempo of the piece or segment changes over its duration, rather than remaining constant.
-
C.
hasTempoVariety
Indicates that an entity exhibits variation or changes in tempo rather than maintaining a constant speed.
-
D.
hasTempoMarking
Indicates that a musical passage, piece, or event is associated with a specific tempo indication or marking.
-
E.
hasTempoOrientation
Indicates that one entity is characterized by a particular temporal direction or alignment (such as past-, present-, or future-oriented) in relation to another entity or 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 30, 2026, 11:57 p.m.