Triple
T28276415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Comes Quickly |
E713005
|
entity |
| Predicate | hasNotableRemixer |
P66064
|
FINISHED |
| Object | Shep Pettibone |
—
|
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: Shep Pettibone | Statement: [Love Comes Quickly, hasNotableRemixer, Shep Pettibone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableRemixer Context triple: [Love Comes Quickly, hasNotableRemixer, Shep Pettibone]
-
A.
hasRemixProducer
Indicates that one entity serves as the producer responsible for creating a remix version of another entity (typically a musical work).
-
B.
notableRemixBy
chosen
Indicates that one creative work has a particularly recognized or significant remix created by a specified artist or entity.
-
C.
hasRemixed
Indicates that one entity has created a new version or adaptation of another entity by remixing it.
-
D.
hasRemix
Indicates that one creative work is a remix version derived from or based on another work.
-
E.
hasRemixFeaturing
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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: April 27, 2026, 11:20 p.m.