Triple
T31434005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MWV A 14 |
E801873
|
entity |
| Predicate | catalogueForWorkBy |
P104390
|
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 A 14, catalogueForWorkBy, Felix Mendelssohn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueForWorkBy Context triple: [MWV A 14, catalogueForWorkBy, Felix Mendelssohn]
-
A.
workCatalogue
Indicates a relationship where a work is included in, documented by, or associated with a specific catalogue.
-
B.
workCatalogueNumberOfWork
Indicates the catalogue number assigned to a specific work within a cataloging or classification system.
-
C.
catalogueFor
Indicates that one entity serves as a catalog or organized listing that describes, indexes, or inventories another entity.
-
D.
workCatalogueScope
Indicates that a work is included within the defined scope or coverage of a particular catalogue.
-
E.
workCatalogueGrouping
chosen
Indicates a grouping relationship that associates a work with a specific catalogue or cataloguing system in which it is organized or referenced.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 30, 2026, 9 p.m.