Triple
T32698119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TNT |
E836068
|
entity |
| Predicate | hasSubgenreRole |
P199149
|
FINISHED |
| Object | pioneer of Scandinavian melodic 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: pioneer of Scandinavian melodic metal | Statement: [TNT, hasSubgenreRole, pioneer of Scandinavian melodic metal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubgenreRole Context triple: [TNT, hasSubgenreRole, pioneer of Scandinavian melodic metal]
-
A.
isAssociatedWithSubgenre
Indicates that one entity has a connection or linkage to a specific subgenre of a broader category.
-
B.
hasSubrole
Indicates that one role functions as a more specific, subordinate, or specialized version of another broader role.
-
C.
hasNotableSubgenre
Indicates that one genre is recognized as a particularly significant or prominent subgenre of another genre.
-
D.
hasGenreInRoles
Indicates that an entity participates in roles associated with a particular genre or set of genres.
-
E.
hasGenreRelation
Indicates that there is an association between an entity and a specific genre, specifying the type or category it belongs to.
- F. None of above. chosen
Provenance (4 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69ff234e63648190a7b09a161029c8e2 |
completed | May 9, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:10 a.m.