Triple
T3127429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violent Crimes |
E65330
|
entity |
| Predicate | lyricalMood |
P45521
|
FINISHED |
| Object | emotionally charged |
—
|
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: emotionally charged | Statement: [Violent Crimes, lyricalMood, emotionally charged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricalMood Context triple: [Violent Crimes, lyricalMood, emotionally charged]
-
A.
lyricalPerspective
Indicates the narrative or point of view from which lyrics are expressed in a song or vocal piece.
-
B.
lyricalPhrase
Indicates that one entity is a lyrical phrase or line that is part of, derived from, or associated with another entity such as a song, poem, or musical work.
-
C.
lyricFocus
Indicates that the primary emphasis or subject of the lyrics is centered on a particular entity or theme.
-
D.
hasLyricalStyle
Indicates that one entity possesses or is characterized by a particular lyrical style in relation to another entity or context.
-
E.
hasLyricalTheme
Indicates that one entity (typically a creative work) features or is characterized by a particular lyrical subject, topic, or theme.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada546a6648190bc4bc3e599e6aa95 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f7c21c819087e9992f5fe30a37 |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.