Triple
T9871811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 5 in E minor, Op. 64 |
E239973
|
entity |
| Predicate | motivicFeature |
P41002
|
FINISHED |
| Object | recurring fate motif |
—
|
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: recurring fate motif | Statement: [Symphony No. 5 in E minor, Op. 64, motivicFeature, recurring fate motif]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motivicFeature Context triple: [Symphony No. 5 in E minor, Op. 64, motivicFeature, recurring fate motif]
-
A.
featuresMotif
chosen
Indicates that something contains, incorporates, or prominently includes a particular recurring motif or pattern.
-
B.
primaryMotif
Indicates that one entity serves as the main recurring theme or dominant motif associated with another entity.
-
C.
featuresMood
Indicates that something includes, presents, or conveys a particular mood or emotional atmosphere.
-
D.
usesMotifsFrom
Indicates that one entity incorporates or draws upon recurring themes, patterns, or elements that originate from another entity.
-
E.
metricalFeature
Indicates a relationship where one entity specifies or characterizes a metrical property or pattern of 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_69ca84e8a0788190b9061811d50fd554 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3f5cc948190b03186b867c92229 |
completed | April 2, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:36 p.m.