Triple
T31433951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MWV O 7 |
E801871
|
entity |
| Predicate | composerOfCataloguedWork |
P190680
|
FINISHED |
| Object | Felix Mendelssohn |
—
|
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: Felix Mendelssohn | Statement: [MWV O 7, composerOfCataloguedWork, Felix Mendelssohn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composerOfCataloguedWork Context triple: [MWV O 7, composerOfCataloguedWork, Felix Mendelssohn]
-
A.
composerOfDepictingWork
Indicates that an entity is the composer of a musical work that is itself a depiction or representation of another entity or subject.
-
B.
composerOfRelatedWorks
Indicates that an entity is the composer of works that are related to another specified work or set of works.
-
C.
composerOfSourceWork
Indicates that an entity is the composer who created the original source work on which another work is based.
-
D.
composerOfMainWork
Indicates that one entity is the composer who created the primary or main work associated with another entity.
-
E.
authorWorkCreator
Indicates that an entity is the creator (author) responsible for producing a particular work.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: April 30, 2026, 9 p.m.