Triple
T13977803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We Will Rock You |
E336230
|
entity |
| Predicate | featuresRhythm |
P112024
|
FINISHED |
| Object | stomp-stomp-clap |
—
|
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: stomp-stomp-clap | Statement: [We Will Rock You, featuresRhythm, stomp-stomp-clap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresRhythm Context triple: [We Will Rock You, featuresRhythm, stomp-stomp-clap]
-
A.
featuresRiff
Indicates that something includes or prominently showcases a specific musical riff.
-
B.
featuresCounterMelody
Indicates that the subject includes or incorporates a secondary melodic line that complements and contrasts with the main melody.
-
C.
featuresDrumMachine
Indicates that something includes or makes use of a drum machine as part of its composition or functionality.
-
D.
featuresMood
Indicates that something includes, presents, or conveys a particular mood or emotional atmosphere.
-
E.
featuresBeatSwitch
Indicates that one entity includes or incorporates a change in rhythmic pattern or beat, typically marking a transition within a sequence or composition.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e9fc7248190a9f26e253286ac3c |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
| PDg | Predicate description generation | batch_69de01ed2098819088ec45069f6f2609 |
completed | April 14, 2026, 8:59 a.m. |
Created at: April 9, 2026, 10:18 p.m.