Triple
T22537016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Red |
E557181
|
entity |
| Predicate | hasVocalShoutsSampledBy |
P50832
|
FINISHED |
| Object | numerous hip hop 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: numerous hip hop artists | Statement: [Long Red, hasVocalShoutsSampledBy, numerous hip hop artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVocalShoutsSampledBy Context triple: [Long Red, hasVocalShoutsSampledBy, numerous hip hop artists]
-
A.
containsVocalSamplesFrom
chosen
Indicates that one audio work includes vocal samples that originate from another audio work.
-
B.
usesVocalSamples
Indicates that one entity incorporates recorded vocal sounds from another source into its own audio or musical production.
-
C.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
D.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
E.
hasVoiceIn
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15edbd1ec81908ef26b9e442d1921 |
completed | April 29, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.