Triple
T37233595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F.40 |
E923206
|
entity |
| Predicate | workBWVNumber |
P97958
|
FINISHED |
| Object | BWV 1052 |
—
|
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 1052 | Statement: [F.40, workBWVNumber, BWV 1052]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workBWVNumber Context triple: [F.40, workBWVNumber, BWV 1052]
-
A.
workNumberInBWV
Indicates that a musical work is identified by a specific catalog number within the Bach-Werke-Verzeichnis (BWV) catalog.
-
B.
BWVNumber
chosen
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.
BWVNumberRange
Indicates that a work is identified as belonging to a specified range of Bach-Werke-Verzeichnis (BWV) catalogue numbers.
-
D.
BWVWorkGroup
Indicates a grouping relationship that associates individual Bach-Werke-Verzeichnis (BWV) works into a larger, thematically or structurally related work group.
-
E.
BWVRangeStart
Indicates the starting point or lowest value of a specified BWV (Bach-Werke-Verzeichnis) range associated with a work or set of works.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb4134225081909fd60703b8cae397 |
completed | May 6, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69fb35bf767081908de8345358ca7f44 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.