Triple
T31394680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MWV N 15 |
E800832
|
entity |
| Predicate | usedForCatalogingMendelssohnWorks |
P182420
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MWV N 15, usedForCatalogingMendelssohnWorks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForCatalogingMendelssohnWorks Context triple: [MWV N 15, usedForCatalogingMendelssohnWorks, yes]
-
A.
MendelssohnSymphonyNumbering
Indicates how Mendelssohn’s symphonies are assigned numbers, especially where publication order and composition order differ.
-
B.
catalogInBeethovenWerkverzeichnis
Indicates that a musical work is cataloged in the Beethoven Werkverzeichnis (Beethoven’s thematic or complete works catalog).
-
C.
workNumberInSchubertCatalogue
Indicates that one entity specifies the identifying work number assigned to a composition within the Schubert catalogue for another entity.
-
D.
sectionUsedByBeethoven
Indicates that a musical section is one that was used or employed by Beethoven in his compositions.
-
E.
hasWorkNumberInBachGesellschaft
Indicates that an entity is assigned a specific work number in the Bach-Gesellschaft (BG) catalog of Bach’s compositions.
- F. None of above. chosen
Provenance (4 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: April 29, 2026, 9:19 p.m.