Triple
T29721518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durand (original piano edition) |
E752065
|
entity |
| Predicate | isScoreOf |
P15617
|
FINISHED |
| Object | Pavane pour une infante défunte |
—
|
NE NERFINISHED |
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: Pavane pour une infante défunte | Statement: [Durand (original piano edition), isScoreOf, Pavane pour une infante défunte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isScoreOf Context triple: [Durand (original piano edition), isScoreOf, Pavane pour une infante défunte]
-
A.
isScoreFor
chosen
Indicates that one value represents the score or result associated with a particular entity, event, or performance.
-
B.
isPartOfScoreBy
Indicates that something constitutes a component or segment within a larger score or musical composition.
-
C.
isScoreForCharacter
Indicates that a given score value is associated with, or belongs to, a particular character.
-
D.
isScoreForSetting
Indicates that a particular score value is associated with, or applies to, a specific setting or configuration.
-
E.
hasScoreCharacteristic
Indicates that one entity possesses or is associated with a particular scoring-related characteristic or property.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672fbd174819094642a594a447e47 |
completed | May 2, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:36 p.m.