Triple
T32742139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resurrection |
E837243
|
entity |
| Predicate | associatedWithChoralSymphonyTradition |
—
|
GENERATED |
| Object | yes |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithChoralSymphonyTradition Context triple: [Resurrection, associatedWithChoralSymphonyTradition, yes]
-
A.
usesChorale
Indicates that one entity incorporates or employs a chorale (a hymn-like musical piece) within its structure or content.
-
B.
hasChoralArrangementsBy
Indicates that one entity (typically a musical work) has choral arrangements created or adapted by the specified entity.
-
C.
hasChoralQuality
Indicates that something possesses characteristics typical of choral music, such as multiple voices or parts combining in a coordinated, ensemble-like manner.
-
D.
hasChoralArrangement
Indicates that one entity is a choral arrangement version or setting of another entity (typically an original musical work).
-
E.
associatedWithHymns
Indicates that something has a connection or relationship to hymns, such as being used in, derived from, or thematically linked to them.
- F. None of above. chosen
Provenance (1 batch)
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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:12 a.m.