Triple
T36218972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | String Quartet in D major, Op. 76 No. 5 |
E1047780
|
entity |
| Predicate | formOfFinale |
P83468
|
FINISHED |
| Object | sonata-rondo |
—
|
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: sonata-rondo | Statement: [String Quartet in D major, Op. 76 No. 5, formOfFinale, sonata-rondo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formOfFinale Context triple: [String Quartet in D major, Op. 76 No. 5, formOfFinale, sonata-rondo]
-
A.
formOfFinalMovement
Indicates that one movement serves as the concluding or final section of another movement or larger musical work.
-
B.
finaleForm
Indicates that one entity represents the final or ultimate form, version, or stage of another entity.
-
C.
hasFinale
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
-
D.
originalFinale
Indicates that something serves as the initial or authentic concluding part or ending of another work, event, or sequence.
-
E.
hasFinaleMovement
chosen
Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final movement.
- 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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b57f05888190a255b55b15f6d79d |
completed | May 3, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.