Triple
T11231553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWV 988 |
E265831
|
entity |
| Predicate | workNumberInBWV |
P97961
|
FINISHED |
| Object | 988 |
—
|
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: 988 | Statement: [BWV 988, workNumberInBWV, 988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberInBWV Context triple: [BWV 988, workNumberInBWV, 988]
-
A.
workNumberInMahlerSymphonies
Indicates the specific numbered position a work occupies within the sequence of Mahler’s symphonies.
-
B.
workNumberInComposerOutput
Indicates that a specific work number appears in the output or catalog produced by a particular composer.
-
C.
HWVNumber
Indicates that an entity is associated with a specific catalog number in the Händel-Werke-Verzeichnis (HWV), identifying its place in the thematic catalog of Handel’s works.
-
D.
workNumberInHaydnOutput
Indicates the ordinal number assigned to a specific work within the catalog of Haydn’s compositions.
-
E.
WagnerCatalogueNumber
Indicates the specific catalogue number assigned to a work in the thematic catalogue of Richard Wagner’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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9026e1c81909456ac946bbba972 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfdf7a88190aae21572e57ef208 |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:30 p.m.