Triple
T23447032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Best of Me |
E565565
|
entity |
| Predicate | mainRemixPerformer |
P30370
|
FINISHED |
| Object | Jadakiss |
—
|
NE NERFINISHED |
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: Jadakiss | Statement: [Best of Me, mainRemixPerformer, Jadakiss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRemixPerformer Context triple: [Best of Me, mainRemixPerformer, Jadakiss]
-
A.
remixArtist
chosen
Indicates that one entity is the artist who created a remix version of a work originally produced by another entity.
-
B.
hasRemix
Indicates that one creative work is a remix version derived from or based on another work.
-
C.
isRemixWith
Indicates that one creative work is a remix created in collaboration with, or incorporating elements from, another specific work.
-
D.
hasRemixProducer
Indicates that one entity serves as the producer responsible for creating a remix version of another entity (typically a musical work).
-
E.
samplePerformer
Indicates that an entity performs, executes, or is responsible for producing a given sample (such as a data sample, test sample, or media sample).
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a649f7e8819080aeb120afd57aad |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:51 p.m.