Triple
T13698929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Din Da Da |
E328463
|
entity |
| Predicate | hasCoverVersionsIn |
P106515
|
FINISHED |
| Object | hip hop |
—
|
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: hip hop | Statement: [Din Da Da, hasCoverVersionsIn, hip hop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverVersionsIn Context triple: [Din Da Da, hasCoverVersionsIn, hip hop]
-
A.
hasCoverVersions
Indicates that a musical work has one or more recorded versions performed or produced by artists other than the original creator.
-
B.
hasCoverVersionPerformer
Indicates that an entity is the performer of a cover version of another entity’s original work.
-
C.
hasCoverVersionInGenre
chosen
Indicates that an entity has at least one cover version that is performed or produced within a specified musical genre.
-
D.
hasRemixOrCovers
Indicates that one creative work is a remix or cover version of another work.
-
E.
hasCoverArtVariant
Indicates that an item has an alternative version of its cover artwork distinct from the primary cover.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc878b57c819094e7ea6d1a64211f |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.