Triple
T8770567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rapsodie espagnole |
E208447
|
entity |
| Predicate | tempoIndicationOfSecondMovement |
P40272
|
FINISHED |
| Object | Assez vif |
—
|
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: Assez vif | Statement: [Rapsodie espagnole, tempoIndicationOfSecondMovement, Assez vif]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tempoIndicationOfSecondMovement Context triple: [Rapsodie espagnole, tempoIndicationOfSecondMovement, Assez vif]
-
A.
tempoMarkingSecondMovement
chosen
Indicates the tempo marking that applies specifically to the second movement of a musical work.
-
B.
tonalityOfSecondMovement
Indicates the key or tonal center that characterizes the second movement of a musical work.
-
C.
secondMovementTitle
Indicates the title or name given to the second movement of a multi-movement musical work.
-
D.
firstMovementTempoMarking
Indicates the tempo marking associated with the first movement of a work or composition.
-
E.
fourthMovementTempoMarking
Indicates the specified tempo marking used in the fourth movement of a musical work.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f2b08f881909f3d4fab2eda1d67 |
completed | March 31, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:41 p.m.