Triple
T26528976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missa Pro Victoria |
E670766
|
entity |
| Predicate | homageToComposer |
P160609
|
FINISHED |
| Object | Clément Janequin |
—
|
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: Clément Janequin | Statement: [Missa Pro Victoria, homageToComposer, Clément Janequin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homageToComposer Context triple: [Missa Pro Victoria, homageToComposer, Clément Janequin]
-
A.
favoriteComposer
Indicates that one entity is the preferred or most liked composer of another entity.
-
B.
hasMusicalComposer
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
C.
dedicatedComposerTradition
Indicates that a composer is specifically devoted to or closely aligned with a particular musical tradition.
-
D.
partOfComposerOeuvre
Indicates that a musical work belongs to and is included within the overall body of compositions created by a particular composer.
-
E.
hasComposerInResidence
Indicates that an organization or institution has officially appointed a specific composer to serve in a resident or ongoing compositional role.
- F. None of above. chosen
Provenance (4 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613f5ec28819099ec679f636d61d9 |
completed | May 2, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 27, 2026, 1:34 a.m.