Triple
T985360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blitzkrieg Bop |
E21264
|
entity |
| Predicate | hasRiffType |
P22757
|
FINISHED |
| Object | power chord guitar riff |
—
|
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: power chord guitar riff | Statement: [Blitzkrieg Bop, hasRiffType, power chord guitar riff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiffType Context triple: [Blitzkrieg Bop, hasRiffType, power chord guitar riff]
-
A.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
B.
hasArticulationType
Indicates the specific manner or type of connection or joint by which two parts or entities are linked or articulated.
-
C.
hasRhythmicStyle
Indicates that one entity exhibits or is characterized by a particular rhythmic pattern or style in its expression or behavior.
-
D.
hasSegmentType
Indicates that an entity is associated with, or classified by, a particular type or category of segment within a larger structure or sequence.
-
E.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
- 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4959fe48190a78bd811cbc888ab |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2abccbc8190a83af432f89eacf5 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b38630848190bd3898a4f42018ad |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:41 p.m.