Triple
T11753342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavatina: Adagio molto espressivo |
E279460
|
entity |
| Predicate | writtenForEnsemble |
P17036
|
FINISHED |
| Object | string quartet |
—
|
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: string quartet | Statement: [Cavatina: Adagio molto espressivo, writtenForEnsemble, string quartet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenForEnsemble Context triple: [Cavatina: Adagio molto espressivo, writtenForEnsemble, string quartet]
-
A.
sungByEnsemble
Indicates that a musical work or performance is vocally performed by a group of singers acting together as an ensemble.
-
B.
isPartOfEnsemble
Indicates that an entity belongs to, or is a member of, a larger group or ensemble.
-
C.
writtenForPerformer
Indicates that a work was specifically composed or created to be performed by a particular performer or type of performer.
-
D.
intendedEnsemble
chosen
Indicates that one entity is designed, chosen, or specified to function as the ensemble or group counterpart associated with another entity.
-
E.
composedForMusicBy
Indicates that a musical work was specifically created or written by a particular composer.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a50b8a14819092a7397d73f0a8e3 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.