Triple
T31394654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reformation Symphony |
E800831
|
entity |
| Predicate | hasChoraleFinale |
P89195
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Reformation Symphony, hasChoraleFinale, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChoraleFinale Context triple: [Reformation Symphony, hasChoraleFinale, true]
-
A.
hasFinaleWithChoraleElements
chosen
Indicates that the finale of a work includes or is characterized by chorale-style musical elements.
-
B.
usesChorale
Indicates that one entity incorporates or employs a chorale (a hymn-like musical piece) within its structure or content.
-
C.
hasChoralArrangement
Indicates that one entity is a choral arrangement version or setting of another entity (typically an original musical work).
-
D.
closingChoraleFirstVersion
Indicates that the relationship involves the first version of a closing chorale section, typically marking an initial or original form of the concluding choral passage.
-
E.
hasFinale
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: April 29, 2026, 9:19 p.m.