Triple
T29853810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death and the Maiden |
E758132
|
entity |
| Predicate | usesThemeInMovement |
P83682
|
FINISHED |
| Object | slow movement |
—
|
LITERAL FINISHED |
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: slow movement | Statement: [Death and the Maiden, usesThemeInMovement, slow movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesThemeInMovement Context triple: [Death and the Maiden, usesThemeInMovement, slow movement]
-
A.
usesThemeBy
Indicates that one entity incorporates, applies, or is based on a theme that was created, defined, or provided by another entity.
-
B.
usesThemeFrom
chosen
Indicates that one work incorporates, references, or is based on the thematic material of another work.
-
C.
isThemedTo
Indicates that one entity is designed, styled, or conceptually based around the subject, motif, or theme represented by another entity.
-
D.
supportsThemeOf
Indicates that one entity reinforces, aligns with, or contributes to the central theme expressed by another entity.
-
E.
reflectsOnTheme
Indicates that one entity critically considers, analyzes, or comments on the theme expressed or embodied by another entity.
- 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_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 29, 2026, 5:45 p.m.