Triple
T27171745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megawave Records |
E682933
|
entity |
| Predicate | notableArtistReleased |
P192950
|
FINISHED |
| Object | Burning Spear |
—
|
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: Burning Spear | Statement: [Megawave Records, notableArtistReleased, Burning Spear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableArtistReleased Context triple: [Megawave Records, notableArtistReleased, Burning Spear]
-
A.
notableArtistRelease
Indicates that a release (such as an album, single, or work) is created or issued by an artist who is considered notable or prominent.
-
B.
notableArtistLaunched
Indicates that an artist gained significant recognition or prominence as a result of the referenced entity or event.
-
C.
notableArtist
Indicates that the subject is an artist who is widely recognized or distinguished for their work.
-
D.
notableVersionArtist
Indicates that an artist is notably associated with a particular version or rendition of a work, such as a song, recording, or performance.
-
E.
releasedMusicForArtist
chosen
Indicates that an entity (such as a label, platform, or distributor) has issued or made available music created by a particular artist.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
Created at: April 27, 2026, 9:24 a.m.