Triple
T33337761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Like Your Lovin' (Do You Like Mine?) |
E853586
|
entity |
| Predicate | featuresSongSampledByArtist |
P17564
|
FINISHED |
| Object | Beyoncé |
E8374
|
NE 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: Beyoncé | Statement: [I Like Your Lovin' (Do You Like Mine?), featuresSongSampledByArtist, Beyoncé]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSongSampledByArtist Context triple: [I Like Your Lovin' (Do You Like Mine?), featuresSongSampledByArtist, Beyoncé]
-
A.
featuresSongwriterCovered
Indicates that one entity includes or highlights a songwriter whose work has been covered in a song or performance by another entity.
-
B.
featuresSongwriter
Indicates that a musical work includes or credits a particular person as its songwriter.
-
C.
featuresSongFrom
Indicates that one musical work includes or incorporates a song originating from another source.
-
D.
sampledArtist
chosen
Indicates that one artist has used a portion of another artist’s work (a sample) in their own creation.
-
E.
sampledSongwriter
Indicates that one entity has used or incorporated a portion of another entity’s songwriting or composition as a sample in a new work.
- F. None of above.
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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a019dfc69fc8190b0d80279a6216ba7 |
completed | May 11, 2026, 9:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3551ef01008190bbac5c6bd5991119 |
completed | June 19, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_6a019d54586c81908292d4880db9fad2 |
completed | May 11, 2026, 9:11 a.m. |
Created at: May 1, 2026, 1:34 a.m.