Triple
T36070606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ski Mask the Slump God |
E1043352
|
entity |
| Predicate | collaboratedOnSong |
P119373
|
FINISHED |
| Object | Take A Step Back |
—
|
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: Take A Step Back | Statement: [Ski Mask the Slump God, collaboratedOnSong, Take A Step Back]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaboratedOnSong Context triple: [Ski Mask the Slump God, collaboratedOnSong, Take A Step Back]
-
A.
workedOnSong
Indicates that an entity contributed effort or participation to the creation, production, or performance of a particular song.
-
B.
workedOnSongFor
Indicates that one entity contributed work or effort toward creating, producing, or developing a particular song for another entity or purpose.
-
C.
coveredSongBy
Indicates that one musical work is a cover version performed or recorded by an artist of a song originally created or popularized by another artist.
-
D.
wroteSongWith
chosen
Indicates that two or more entities collaborated in the creation or composition of a song.
-
E.
creditedSongwritingPartnership
Indicates that two or more entities are formally acknowledged as co-writers of a song.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.