Triple
T13229971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prelude in F major, BWV 856 |
E314986
|
entity |
| Predicate | workNumberInBWVCatalog |
P85815
|
FINISHED |
| Object | 856 |
—
|
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: 856 | Statement: [Prelude in F major, BWV 856, workNumberInBWVCatalog, 856]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberInBWVCatalog Context triple: [Prelude in F major, BWV 856, workNumberInBWVCatalog, 856]
-
A.
workCatalogueNumberOfWork
Indicates the catalogue number assigned to a specific work within a cataloging or classification system.
-
B.
workCatalogueNumber
chosen
Indicates the catalog or reference number assigned to a specific work within an organized catalogue or listing.
-
C.
appearsInWorkNumber
Indicates that an entity is featured or occurs within a specific numbered work in a series or collection.
-
D.
workNumbering
Indicates that a specific numbering or cataloging identifier is assigned to a work within a larger collection or system.
-
E.
workNumberInDeRePublica
Indicates that an entity has a specific work number or index within the collection or edition of "De Re Publica."
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d336ae08190bfc118cfbefddf84 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:21 p.m.