Triple
T31999739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suite en fa, Op. 33 |
E817090
|
entity |
| Predicate | hasTempoContrastBetweenMovements |
P46727
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Suite en fa, Op. 33, hasTempoContrastBetweenMovements, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTempoContrastBetweenMovements Context triple: [Suite en fa, Op. 33, hasTempoContrastBetweenMovements, yes]
-
A.
hasTempoVariety
Indicates that an entity exhibits variation or changes in tempo rather than maintaining a constant speed.
-
B.
hasTempoChanges
chosen
Indicates that the tempo of the piece or segment changes over its duration, rather than remaining constant.
-
C.
hasTempoCategory
Indicates that something is associated with a particular tempo classification or speed category.
-
D.
movement6Tempo
Indicates the tempo or speed at which the sixth movement of a work is performed or proceeds.
-
E.
movement7Tempo
Indicates the tempo at which the seventh movement of a work is performed or intended to be played.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 1, 2026, 12:14 a.m.