Triple
T35290985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWV 851 |
E1019223
|
entity |
| Predicate | isPartOfCanonicalRepertoire |
P105958
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [BWV 851, isPartOfCanonicalRepertoire, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCanonicalRepertoire Context triple: [BWV 851, isPartOfCanonicalRepertoire, true]
-
A.
includedInStandardRepertoire
chosen
Indicates that something is part of the commonly accepted or regularly used set within a particular standard repertoire.
-
B.
statusWithinRepertoire
Indicates that a particular status or state is included as part of an entity’s defined repertoire of possible statuses.
-
C.
repertoireIncludes
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
D.
associatedRepertoire
Indicates a relationship where one entity is linked to or connected with a particular repertoire, such as a set of works, skills, or performances.
-
E.
hasPartInCanonization
Indicates that an entity participated in or contributed to the process of canonization of another entity.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: May 3, 2026, 4:03 p.m.