Triple
T6271790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sent from Up Above |
E140551
|
entity |
| Predicate | vocalCredit |
P44280
|
FINISHED |
| Object | lead vocals by Mariah Carey |
—
|
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: lead vocals by Mariah Carey | Statement: [Sent from Up Above, vocalCredit, lead vocals by Mariah Carey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalCredit Context triple: [Sent from Up Above, vocalCredit, lead vocals by Mariah Carey]
-
A.
hasVocalPerformanceBy
chosen
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
B.
vocalistIn
Indicates that a person serves as a vocalist (singer) in a particular musical group, band, or ensemble.
-
C.
hasBackingVocals
Indicates that one musical performance, track, or part includes supporting vocal contributions accompanying a primary vocal line.
-
D.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
E.
vocalPerformanceNotedFor
Indicates that a particular vocal performance is recognized or distinguished for a specific quality, feature, or characteristic.
- 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_69c008cabc4081909723e2547c9d6cc0 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063bca5488190b9da3c037cfc7953 |
completed | March 22, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69c05606fb50819082d1a5a91e5030b6 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.