Triple
T26194099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Songs to Warm the Heart |
E655047
|
entity |
| Predicate | featuresBacking |
P153171
|
FINISHED |
| Object | vocal 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: vocal harmonies | Statement: [Songs to Warm the Heart, featuresBacking, vocal harmonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBacking Context triple: [Songs to Warm the Heart, featuresBacking, vocal harmonies]
-
A.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
-
B.
featuresDemon
Indicates that an entity includes, depicts, or prominently involves a demon.
-
C.
featuresSupplication
Indicates that one entity performs or exhibits an act of earnest pleading, begging, or humble request directed toward another entity.
-
D.
featuresSuit
Indicates that one entity includes or presents a particular suit (e.g., clothing, armor, or outfit) as a notable component or attribute.
-
E.
featuresBackingEnsemble
chosen
Indicates that an entity includes or is accompanied by a backing ensemble supporting its primary performance or presentation.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 26, 2026, 8:45 p.m.