Triple
T8770566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rapsodie espagnole |
E208447
|
entity |
| Predicate | tempoIndicationOfFirstMovement |
P40356
|
FINISHED |
| Object | Très modéré |
—
|
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: Très modéré | Statement: [Rapsodie espagnole, tempoIndicationOfFirstMovement, Très modéré]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tempoIndicationOfFirstMovement Context triple: [Rapsodie espagnole, tempoIndicationOfFirstMovement, Très modéré]
-
A.
firstMovementTempoMarking
chosen
Indicates the tempo marking associated with the first movement of a work or composition.
-
B.
firstMovement
Indicates that an entity represents the initial or earliest movement, action, or motion in a sequence of movements.
-
C.
tempoMarkingSecondMovement
Indicates the tempo marking that applies specifically to the second movement of a musical work.
-
D.
firstMovementForm
Indicates that the subject is in the form or configuration it has during its first movement or initial phase of motion.
-
E.
tonalityOfFirstMovement
Indicates the key or tonal center in which the first movement of a musical work is composed.
- 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.