Triple
T29853829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death and the Maiden |
E758132
|
entity |
| Predicate | hasOpusLikeDesignation |
P66233
|
FINISHED |
| Object | D 810 |
—
|
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: D 810 | Statement: [Death and the Maiden, hasOpusLikeDesignation, D 810]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpusLikeDesignation Context triple: [Death and the Maiden, hasOpusLikeDesignation, D 810]
-
A.
hasOpusForm
Indicates that an entity (such as a work or composition) is associated with a specific opus form or cataloging format.
-
B.
hasOpusNumber
chosen
Indicates that a musical work is associated with a specific opus number assigned to it, typically denoting its place in a composer’s catalog.
-
C.
hasOpusGroup
Indicates that a work or composition belongs to, or is categorized within, a particular opus grouping or collection.
-
D.
hasOpusSetTitle
Indicates that an opus (a musical or artistic work) is associated with a specific set title under which it is grouped or published.
-
E.
hasOrchestralFeature
Indicates that something includes, exhibits, or is characterized by a notable orchestral element or component.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 5:45 p.m.