Triple
T23391704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5 Star |
E594035
|
entity |
| Predicate | featuredInRemix |
P75509
|
FINISHED |
| Object | 5 Star (remix) |
—
|
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: 5 Star (remix) | Statement: [5 Star, featuredInRemix, 5 Star (remix)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredInRemix Context triple: [5 Star, featuredInRemix, 5 Star (remix)]
-
A.
hasRemixFeaturing
chosen
Indicates that an original work has a remix version that features an additional artist or artists not present in the original.
-
B.
hasRemix
Indicates that one creative work is a remix version derived from or based on another work.
-
C.
featuredOnSong
Indicates that an entity (such as an artist) appears as a guest or secondary contributor on a particular song.
-
D.
notableRemixBy
Indicates that one creative work has a particularly recognized or significant remix created by a specified artist or entity.
-
E.
featuredIn
Indicates that one entity appears or is prominently included within another entity, such as a person, work, or item being showcased in a larger work, event, or context.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a49ca5a0819091b74ca59e7fedd4 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:36 p.m.