Triple
T29663441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reggatta de Blanc |
E750466
|
entity |
| Predicate | hasGenreFusion |
P14839
|
FINISHED |
| Object | new wave and reggae |
—
|
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: new wave and reggae | Statement: [Reggatta de Blanc, hasGenreFusion, new wave and reggae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenreFusion Context triple: [Reggatta de Blanc, hasGenreFusion, new wave and reggae]
-
A.
isOnGenreBlendingAlbum
Indicates that something (typically a song or track) appears on an album characterized by blending or combining multiple musical genres.
-
B.
hasRemixGenre
Indicates that a work or track has a remix version characterized by a particular musical genre.
-
C.
hasGenreFeature
Indicates that something possesses a characteristic, element, or trait associated with a particular genre.
-
D.
musicFusionOf
chosen
Indicates a relationship where one musical work, style, or element is created by combining or blending two or more distinct musical sources or genres.
-
E.
hasGenreInfluenceOn
Indicates that one genre has a notable impact on shaping or influencing the characteristics, style, or development of another genre.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 28, 2026, 7 p.m.