Triple
T13220055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 7 Days of Funk |
E314726
|
entity |
| Predicate | hasSpotifyId |
P108585
|
FINISHED |
| Object | 1p0t2rU9w0lVvYlIk5dUvA |
—
|
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: 1p0t2rU9w0lVvYlIk5dUvA | Statement: [7 Days of Funk, hasSpotifyId, 1p0t2rU9w0lVvYlIk5dUvA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpotifyId Context triple: [7 Days of Funk, hasSpotifyId, 1p0t2rU9w0lVvYlIk5dUvA]
-
A.
isOnSpotify
Indicates that a given entity (such as a song, album, or artist) is available or present on the Spotify platform.
-
B.
musicBrainzID
Indicates that an entity is associated with a specific identifier in the MusicBrainz database that uniquely references it.
-
C.
discogsID
Indicates that an entity is associated with a specific identifier used by the Discogs music database to reference it uniquely.
-
D.
hasISRC
Indicates that a musical recording is associated with a specific International Standard Recording Code (ISRC) that uniquely identifies it.
-
E.
allMusicID
Indicates a unique identifier that associates an entity with a specific music item or record in a music-related dataset or system.
- F. None of above. chosen
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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf581508190883033f0c961736a |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:18 p.m.