Triple
T17183546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortunately Gone |
E417039
|
entity |
| Predicate | hasDiscogsWorkId |
P45529
|
FINISHED |
| Object | (unknown exact ID) |
—
|
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: (unknown exact ID) | Statement: [Fortunately Gone, hasDiscogsWorkId, (unknown exact ID)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscogsWorkId Context triple: [Fortunately Gone, hasDiscogsWorkId, (unknown exact ID)]
-
A.
discogsID
chosen
Indicates that an entity is associated with a specific identifier used by the Discogs music database to reference it uniquely.
-
B.
hasGoodreadsWorkId
Indicates that an entity is associated with a specific Goodreads work identifier linking it to a work entry in the Goodreads database.
-
C.
hasDiscographyWith
Indicates a relationship where two or more musical entities are associated through a shared or jointly produced discography.
-
D.
hasDiscographyIn
Indicates that an entity has released or contributed to musical recordings within a particular region, market, or catalog context.
-
E.
musicBrainzID
Indicates that an entity is associated with a specific identifier in the MusicBrainz database that uniquely references it.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42d9416a48190a5930fcd6008dbaa |
completed | April 19, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.