Triple
T19001202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I'll Go to My Grave Loving You |
E464955
|
entity |
| Predicate | vocalArrangementFeature |
P37619
|
FINISHED |
| Object | rich harmonies |
—
|
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: rich harmonies | Statement: [I'll Go to My Grave Loving You, vocalArrangementFeature, rich harmonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalArrangementFeature Context triple: [I'll Go to My Grave Loving You, vocalArrangementFeature, rich harmonies]
-
A.
vocalArrangement
chosen
Indicates the specific way vocal parts or voices are organized, structured, and combined within a musical work or performance.
-
B.
featuresVocalEnsemble
Indicates that something includes or presents a group of vocal performers singing together.
-
C.
vocalForm
Indicates the specific vocal or phonetic form in which something (such as a word, sound, or utterance) is expressed.
-
D.
vocalConfiguration
Indicates how an entity’s vocal or sound-producing characteristics are arranged or specified in relation to another entity or context.
-
E.
featuresVocalHarmonyBy
Indicates that the subject work includes vocal harmony performances contributed by the specified artist or group.
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6863cf4819096e471d19f9a714c |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.