Triple
T29028541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III. Rondo: Allegro non troppo |
E737661
|
entity |
| Predicate | associatedKeyOfWork |
P181618
|
FINISHED |
| Object | D minor |
—
|
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: D minor | Statement: [III. Rondo: Allegro non troppo, associatedKeyOfWork, D minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedKeyOfWork Context triple: [III. Rondo: Allegro non troppo, associatedKeyOfWork, D minor]
-
A.
associatedWorkKey
Indicates that there is a connection or linkage between one work and another related work, typically identifying the related work by a key or identifier.
-
B.
keyWorkAssociation
chosen
Indicates a relationship where a key is associated with a specific work, such as a musical composition, document, or project, typically for identification, access, or classification purposes.
-
C.
associatedWork
Indicates that there exists a related or connected work (such as a publication, creative piece, or project) that is meaningfully linked to the subject.
-
D.
associatedWithInWork
Indicates that two entities are connected or related to each other within the context of a particular work or project.
-
E.
associatedWithWorkOf
Indicates that one entity has a connection or involvement with the work, creation, or output produced by another entity.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a02fcbe03d0819082d3dd715ed41623 |
completed | May 12, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_6a02fc62138081908d2dbc5db7541d13 |
completed | May 12, 2026, 10:09 a.m. |
Created at: April 28, 2026, 9:54 a.m.