Triple
T35216297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leathermouth |
E1016822
|
entity |
| Predicate | lyricsCharacterizedBy |
P140745
|
FINISHED |
| Object | politically charged themes |
—
|
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: politically charged themes | Statement: [Leathermouth, lyricsCharacterizedBy, politically charged themes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lyricsCharacterizedBy Context triple: [Leathermouth, lyricsCharacterizedBy, politically charged themes]
-
A.
lyricCharacterization
chosen
Indicates how the lyrics portray, describe, or characterize a subject within a song or musical work.
-
B.
lyricalCharacter
Indicates that one entity is the character or persona expressed or portrayed in the lyrics of the other entity (such as a song or poem).
-
C.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
D.
notableSongCharacteristic
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
-
E.
lyricType
Indicates the specific category or role that a lyric plays within a musical or lyrical work (e.g., verse, chorus, bridge).
- 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.