Triple
T35112885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWV 848 |
E1013343
|
entity |
| Predicate | primaryCatalogue |
P88854
|
FINISHED |
| Object | Bach-Werke-Verzeichnis |
E52614
|
NE 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: Bach-Werke-Verzeichnis | Statement: [BWV 848, primaryCatalogue, Bach-Werke-Verzeichnis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCatalogue Context triple: [BWV 848, primaryCatalogue, Bach-Werke-Verzeichnis]
-
A.
primaryProduct
Indicates that one entity is the main or most important product associated with, produced by, or offered by another entity.
-
B.
catalogueFor
chosen
Indicates that one entity serves as a catalog or organized listing that describes, indexes, or inventories another entity.
-
C.
catalog
Indicates the action of systematically listing, organizing, or recording items or information into a structured collection or database.
-
D.
cataloguePrefix
Indicates that one entity serves as the initial or leading segment of another entity’s catalogue identifier or listing code.
-
E.
ownedCatalog
Indicates that one entity possesses or has ownership rights over a particular catalog.
- F. None of above.
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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37d001b9e48190952a6a89f0a367d6 |
completed | June 21, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.