Triple
T35094241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opus 8 |
E1012819
|
entity |
| Predicate | isPartOfComposerCatalogue |
P19933
|
FINISHED |
| Object | Erich Wolfgang Korngold catalogue |
—
|
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: Erich Wolfgang Korngold catalogue | Statement: [Opus 8, isPartOfComposerCatalogue, Erich Wolfgang Korngold catalogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfComposerCatalogue Context triple: [Opus 8, isPartOfComposerCatalogue, Erich Wolfgang Korngold catalogue]
-
A.
associatedComposerCatalog
Indicates a relationship between a work and a specific catalog of that composer’s works with which it is associated.
-
B.
discoveredInCatalogue
Indicates that an entity was identified or first recognized through information found in a specific catalogue.
-
C.
partOfComposerOeuvre
Indicates that a musical work belongs to and is included within the overall body of compositions created by a particular composer.
-
D.
belongsToCatalogOf
chosen
Indicates that one item is included within, or is a member of, a particular catalog or collection.
-
E.
usedInCatalogue
Indicates that something is included or referenced as an entry within a catalogue.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 3, 2026, 4:01 p.m.