Triple
T24403135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tokens |
E615233
|
entity |
| Predicate | songOriginallyBasedOn |
P138290
|
FINISHED |
| Object | Mbube |
—
|
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: Mbube | Statement: [The Tokens, songOriginallyBasedOn, Mbube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: songOriginallyBasedOn Context triple: [The Tokens, songOriginallyBasedOn, Mbube]
-
A.
basedOnSongFrom
chosen
Indicates that one creative work is derived from, adapted from, or otherwise based on a particular song.
-
B.
basedOnSongBy
Indicates that one entity is derived from, adapted from, or otherwise created using a particular song as its source or inspiration.
-
C.
originalSong
Indicates that one entity is the source or initial version of a song from which another entity (such as a cover, remix, or adaptation) is derived.
-
D.
originalMusical
Indicates that a work is the initial or primary musical composition from which other versions, adaptations, or performances are derived.
-
E.
inspiredSong
Indicates that one entity (such as an event, person, or work) served as the creative inspiration or motivating influence for the creation of a particular 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294dc1240819085aba9a8c2e07f42 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.