Triple
T24722022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love All Over Me |
E612328
|
entity |
| Predicate | hasOfficialRemix |
P75509
|
FINISHED |
| Object | Love All Over Me (remix featuring Gucci Mane) |
—
|
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: Love All Over Me (remix featuring Gucci Mane) | Statement: [Love All Over Me, hasOfficialRemix, Love All Over Me (remix featuring Gucci Mane)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialRemix Context triple: [Love All Over Me, hasOfficialRemix, Love All Over Me (remix featuring Gucci Mane)]
-
A.
hasRemix
Indicates that one creative work is a remix version derived from or based on another work.
-
B.
hasRemixed
Indicates that one entity has created a new version or adaptation of another entity by remixing it.
-
C.
hasRemixVariant
Indicates that one entity is a remix version or reworked variant of another entity.
-
D.
hasRemixProducer
Indicates that one entity serves as the producer responsible for creating a remix version of another entity (typically a musical work).
-
E.
hasRemixFeaturing
chosen
Indicates that an original work has a remix version that features an additional artist or artists not present in the original.
- 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 3:41 a.m.