Triple
T11753139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beethoven piano sonatas |
E279455
|
entity |
| Predicate | coreRepertoireFor |
P38497
|
FINISHED |
| Object | concert 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: concert pianists | Statement: [Beethoven piano sonatas, coreRepertoireFor, concert pianists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreRepertoireFor Context triple: [Beethoven piano sonatas, coreRepertoireFor, concert pianists]
-
A.
centralRepertoireFor
chosen
Indicates that something serves as a primary or core collection of works, items, or elements for a particular entity or context.
-
B.
featuresRepertoireType
Indicates that something includes or is associated with a particular type or category of repertoire.
-
C.
publicRepertoireStatus
Indicates that an entity’s repertoire or collection is designated as publicly visible or accessible rather than private or restricted.
-
D.
repertoireIncludes
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
E.
repertoireLanguage
Indicates that the associated entity’s repertoire (e.g., works, performances, or outputs) is expressed or available in a particular language.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a509c2448190b0deb7ed29c3a73f |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.