Triple

T23732899
Position Surface form Disambiguated ID Type / Status
Subject Wheelhouse E586455 entity
Predicate hasControversialSong P81772 FINISHED
Object Accidental Racist NE NERFINISHED

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: Accidental Racist | Statement: [Wheelhouse, hasControversialSong, Accidental Racist]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasControversialSong
Context triple: [Wheelhouse, hasControversialSong, Accidental Racist]
  • A. hasControversialLyrics
    Indicates that the lyrics associated with an entity are considered contentious, offensive, or likely to provoke public disagreement or debate.
  • B. hasControversialAspect chosen
    Indicates that something includes an element, feature, or aspect that is disputed, debated, or likely to cause disagreement or public criticism.
  • C. hasProtestSong
    Indicates that an entity (such as an artist, movement, or event) is associated with or characterized by a protest song.
  • D. hasSongAbout
    Indicates that one entity has created, features, or is associated with a song whose subject or theme is about another entity.
  • E. controversialBecause
    Indicates that one entity is considered controversial specifically due to, or as a result of, its relationship with or association to another entity.
  • 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_69e24907dc9c8190be074c9c96a0ec2d completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1bace7ce88190a7d4ce6e430bbdfa completed April 29, 2026, 8:01 a.m.
PD Predicate disambiguation batch_69f155e4b1148190836ede4741dcb888 completed April 29, 2026, 12:50 a.m.
Created at: April 17, 2026, 7:10 p.m.