Triple
T13154571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugue in E minor, BWV 855 |
E312548
|
entity |
| Predicate | isPartOfStandardRepertoireFor |
P105958
|
FINISHED |
| Object | pianists |
—
|
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: pianists | Statement: [Fugue in E minor, BWV 855, isPartOfStandardRepertoireFor, pianists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfStandardRepertoireFor Context triple: [Fugue in E minor, BWV 855, isPartOfStandardRepertoireFor, pianists]
-
A.
includedInStandardRepertoire
chosen
Indicates that something is part of the commonly accepted or regularly used set within a particular standard repertoire.
-
B.
repertoireIncludes
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
C.
notabilityInRepertoire
Indicates that a work holds particular significance or prominence within an entity’s repertoire.
-
D.
isEducationalRepertoire
Indicates that something constitutes a set of materials, activities, or practices used for educational or instructional purposes.
-
E.
isPartOfEnsemble
Indicates that an entity belongs to, or is a member of, a larger group or ensemble.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:11 p.m.