Triple
T35408379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OMI |
E1023431
|
entity |
| Predicate | notableRemixOfSong |
P9639
|
FINISHED |
| Object | Cheerleader (Felix Jaehn Remix) |
E1023426
|
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: Cheerleader (Felix Jaehn Remix) | Statement: [OMI, notableRemixOfSong, Cheerleader (Felix Jaehn Remix)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRemixOfSong Context triple: [OMI, notableRemixOfSong, Cheerleader (Felix Jaehn Remix)]
-
A.
notableRemixBy
Indicates that one creative work has a particularly recognized or significant remix created by a specified artist or entity.
-
B.
hasRemixed
Indicates that one entity has created a new version or adaptation of another entity by remixing it.
-
C.
notableTrack
Indicates that a particular track (such as a song or recording) is especially significant, well-known, or prominent in relation to the subject.
-
D.
hasRemix
chosen
Indicates that one creative work is a remix version derived from or based on another work.
-
E.
notableTune
Indicates that a tune is especially significant, well-known, or characteristic in relation to a particular entity.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3852d85e2c8190a85921c202cab4cd |
completed | June 21, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.