Triple
T1525120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Songs of Joy & Peace |
E32316
|
entity |
| Predicate | hasContributionFrom |
P30146
|
FINISHED |
| Object | various artists |
—
|
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: various artists | Statement: [Songs of Joy & Peace, hasContributionFrom, various artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContributionFrom Context triple: [Songs of Joy & Peace, hasContributionFrom, various artists]
-
A.
tributeFrom
Indicates that one entity pays or provides tribute, often as a sign of submission or obligation, to another entity.
-
B.
tributeTo
Indicates that one entity is created, given, or dedicated as a mark of respect, admiration, or honor toward another entity.
-
C.
hasContributorProgram
Indicates that an entity operates or participates in a formal program through which contributors can submit work, content, or support.
-
D.
creditedFor
Indicates that one entity is acknowledged as the source, contributor, or originator responsible for another entity (such as a work, achievement, or outcome).
-
E.
tributeMethod
Indicates the means or manner by which tribute is given, delivered, or fulfilled between parties.
- F. None of above. chosen
Provenance (4 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93d4756888190bf3872154de11539 |
completed | March 5, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69a907ac7ea081908dd95bb5cc3b9847 |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69a93d462f208190b27ef5cd631bce12 |
completed | March 5, 2026, 8:22 a.m. |
Created at: March 4, 2026, 7:26 p.m.