Triple

T30866199
Position Surface form Disambiguated ID Type / Status
Subject Requiem pour un con E786205 entity
Predicate hasBitingLyrics P123542 FINISHED
Object true 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: true | Statement: [Requiem pour un con, hasBitingLyrics, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBitingLyrics
Context triple: [Requiem pour un con, hasBitingLyrics, true]
  • A. hasControversialLyrics
    Indicates that the lyrics associated with an entity are considered contentious, offensive, or likely to provoke public disagreement or debate.
  • B. hasWittyLyrics chosen
    Indicates that the subject contains or is characterized by clever, humorous, or sharply amusing lyrics.
  • C. hasAggressiveVocals
    Indicates that the subject produces or features vocals delivered in an intense, harsh, or forceful manner.
  • D. hasRomanticLyrics
    Indicates that the subject contains or features lyrics expressing romantic feelings, themes, or relationships.
  • E. hasLyricsIn
    Indicates that the lyrics of a work are written or available in a specified language.
  • 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_69f224b9df2c819086f55f8bcf7f382e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6f8565134819096aac0175f924a9f completed May 3, 2026, 7:25 a.m.
PD Predicate disambiguation batch_69f6f65fd1d08190b88e5e68ba268500 completed May 3, 2026, 7:16 a.m.
Created at: April 29, 2026, 8:47 p.m.