Triple
T23320989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microphone Fiend |
E591148
|
entity |
| Predicate | hasCoverVersionGenre |
P106515
|
FINISHED |
| Object | rap 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: rap metal | Statement: [Microphone Fiend, hasCoverVersionGenre, rap metal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoverVersionGenre Context triple: [Microphone Fiend, hasCoverVersionGenre, rap metal]
-
A.
hasCoverVersionInGenre
chosen
Indicates that an entity has at least one cover version that is performed or produced within a specified musical genre.
-
B.
hasCoverVersionPerformer
Indicates that an entity is the performer of a cover version of another entity’s original work.
-
C.
hasCoverVersionLanguage
Indicates that a cover version of a work is performed or produced in a specified language.
-
D.
hasCoverVersions
Indicates that a musical work has one or more recorded versions performed or produced by artists other than the original creator.
-
E.
hasCountryCoverVersionBy
Indicates that one entity is a country music cover version of another entity (typically an original song or recording).
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19785ae5481908816b37da95ceb3e |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:07 p.m.