Triple
T37445340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boom (music video) |
E930527
|
entity |
| Predicate | hasMusicGenreOfPerformer |
P63466
|
FINISHED |
| Object | Christian metal |
—
|
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: Christian metal | Statement: [Boom (music video), hasMusicGenreOfPerformer, Christian metal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicGenreOfPerformer Context triple: [Boom (music video), hasMusicGenreOfPerformer, Christian metal]
-
A.
hasArtistGenre
chosen
Indicates that an artist is associated with or categorized under a particular musical or artistic genre.
-
B.
hasGenreArtist
Indicates that an artist is associated with or specializes in a particular genre.
-
C.
hasMusicalArtistType
Indicates that an entity has a specific role or classification as a type of musical artist (e.g., solo artist, band, composer).
-
D.
hasTargetArtistGenre
Indicates that an entity (such as a campaign, recommendation, or product) is aimed at or associated with a specific music artist genre as its intended target.
-
E.
hasMusicalWorkType
Indicates that a musical work is associated with a specific type or category of musical composition.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: May 3, 2026, 4:17 p.m.