Triple
T11019411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Martyre de saint Sébastien |
E260445
|
entity |
| Predicate | hasIncidentalMusic |
P43970
|
FINISHED |
| Object | music by Claude Debussy |
—
|
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: music by Claude Debussy | Statement: [Le Martyre de saint Sébastien, hasIncidentalMusic, music by Claude Debussy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIncidentalMusic Context triple: [Le Martyre de saint Sébastien, hasIncidentalMusic, music by Claude Debussy]
-
A.
incidentalMusicTitle
Indicates that a work serves as incidental music for another work and specifies the title of that associated work.
-
B.
hasMainInstrumentalElements
Indicates that one entity includes or is characterized by the primary instrumental components or parts of another entity.
-
C.
hasMusical
chosen
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
D.
hasSoundtrackCharacteristic
Indicates that a soundtrack possesses a specified quality, feature, or attribute.
-
E.
premiereDateOfIncidentalMusic
Indicates the date on which the incidental music for a work was first publicly premiered.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797a9e8788190a0f45b52bad1bfb5 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.