Triple
T24317964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bach Partitas |
E612873
|
entity |
| Predicate | BWVNumberRange |
P155532
|
FINISHED |
| Object | BWV 825–830 |
—
|
NE NERFINISHED |
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: BWV 825–830 | Statement: [Bach Partitas, BWVNumberRange, BWV 825–830]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BWVNumberRange Context triple: [Bach Partitas, BWVNumberRange, BWV 825–830]
-
A.
BWVRangeStart
Indicates the starting point or lowest value of a specified BWV (Bach-Werke-Verzeichnis) range associated with a work or set of works.
-
B.
BWVNumber
Indicates the catalog number assigned to a musical work in the Bach-Werke-Verzeichnis (BWV) system, specifying its place in the catalog of J.S. Bach’s compositions.
-
C.
BWVRangeEnd
Indicates the ending point or upper bound of a specified BWV (Bach-Werke-Verzeichnis) range in a cataloging or classification context.
-
D.
BWVWorkGroup
Indicates a grouping relationship that associates individual Bach-Werke-Verzeichnis (BWV) works into a larger, thematically or structurally related work group.
-
E.
workNumberInBWV
Indicates that a musical work is identified by a specific catalog number within the Bach-Werke-Verzeichnis (BWV) catalog.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292a916c8819096d018e7ffaf483b |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 1:47 a.m.