Triple
T22577745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Push Thru (Remix) |
E544458
|
entity |
| Predicate | featuresAdditionalGuestArtists |
P93602
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Push Thru (Remix), featuresAdditionalGuestArtists, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresAdditionalGuestArtists Context triple: [Push Thru (Remix), featuresAdditionalGuestArtists, true]
-
A.
numberOfGuestArtists
Indicates the count of guest artists associated with or participating in a particular work, event, or entity.
-
B.
hasGuestVocalists
chosen
Indicates that one or more guest vocalists perform vocals on a work, performance, or recording in addition to the primary artist(s).
-
C.
invitedArtist
Indicates that one entity has extended an invitation to another entity in the role of an artist.
-
D.
recordingArtistOfGuestVocalist
Indicates that an artist is the primary recording artist on a work that features another artist as a guest vocalist.
-
E.
featuresArtistAs
Indicates that one entity includes or presents another entity in the role of an artist (e.g., a work, event, or product featuring a specific artist).
- 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15fedbddc8190bc50458a76f5407d |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:53 p.m.