Triple
T8676551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pavane pour une infante défunte |
E205928
|
entity |
| Predicate | belongsToRepertoireOf |
P3738
|
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: [Pavane pour une infante défunte, belongsToRepertoireOf, pianists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToRepertoireOf Context triple: [Pavane pour une infante défunte, belongsToRepertoireOf, pianists]
-
A.
repertoireIncludes
chosen
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
B.
isPartOfEnsemble
Indicates that an entity belongs to, or is a member of, a larger group or ensemble.
-
C.
publicRepertoireStatus
Indicates that an entity’s repertoire or collection is designated as publicly visible or accessible rather than private or restricted.
-
D.
hasMusicalEnsembleType
Indicates that an entity is associated with or classified as a particular type of musical ensemble.
-
E.
notabilityInRepertoire
Indicates that a work holds particular significance or prominence within an entity’s repertoire.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.