Triple
T31434289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scherzo: Allegro leggierissimo |
E801881
|
entity |
| Predicate | typicalTempoCharacter |
P148387
|
FINISHED |
| Object | very fast |
—
|
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: very fast | Statement: [Scherzo: Allegro leggierissimo, typicalTempoCharacter, very fast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTempoCharacter Context triple: [Scherzo: Allegro leggierissimo, typicalTempoCharacter, very fast]
-
A.
typicalTempoCharacterization
chosen
Indicates how the usual or characteristic tempo of something is described or classified.
-
B.
typicalTempoPattern
Indicates the characteristic or commonly occurring tempo progression or rhythmic pattern associated with an action or event.
-
C.
typicalTempoControl
Indicates that one entity serves as the usual or standard means by which the tempo of another entity (such as a process or activity) is regulated or controlled.
-
D.
commonTempo
Indicates that two or more musical entities share the same tempo or rate of beats per minute.
-
E.
musicalTempo
Indicates the speed or pace at which a piece of music is performed or intended to be performed.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9 p.m.