Triple
T37072124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A New Perspective |
E917608
|
entity |
| Predicate | choralArrangementsFeature |
P79255
|
FINISHED |
| Object | wordless choir |
—
|
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: wordless choir | Statement: [A New Perspective, choralArrangementsFeature, wordless choir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: choralArrangementsFeature Context triple: [A New Perspective, choralArrangementsFeature, wordless choir]
-
A.
hasChoralArrangement
chosen
Indicates that one entity is a choral arrangement version or setting of another entity (typically an original musical work).
-
B.
orchestralArrangement
Indicates that one musical work is arranged or adapted specifically for performance by an orchestra.
-
C.
musicalArrangement
Indicates that one entity is an arrangement or adaptation of another musical work.
-
D.
hasSheetMusicAvailability
Indicates that there exists accessible sheet music associated with the referenced musical work or performance.
-
E.
usesChorale
Indicates that one entity incorporates or employs a chorale (a hymn-like musical piece) within its structure or content.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.