Triple

T38056975
Position Surface form Disambiguated ID Type / Status
Subject De Klassieker E950230 entity
Predicate hasDerogatoryChants P148419 FINISHED
Object yes 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: yes | Statement: [De Klassieker, hasDerogatoryChants, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDerogatoryChants
Context triple: [De Klassieker, hasDerogatoryChants, yes]
  • A. hasDerogatoryChanting chosen
    Indicates that one party directs insulting or abusive chanting toward another party.
  • B. hasChant
    Indicates that an entity is associated with or characterized by a particular chant.
  • C. hasSpokenChants
    Indicates that an entity has uttered or recited ritualistic or formulaic chants, typically as part of a ceremonial, religious, or magical practice.
  • D. hasFanChantPotential
    Indicates that something (such as a song, phrase, or performance element) is well-suited to be adopted and enthusiastically chanted by a crowd or fanbase.
  • E. hasChantingStyle
    Indicates that an entity is associated with or characterized by a particular style or manner of chanting.
  • 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_69f76f01e63c819093b6012fc974f35a completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69ffc3f0b19c8190b5a749bc3cad21dd completed May 9, 2026, 11:32 p.m.
PD Predicate disambiguation batch_69ffc1b882808190932b2d43ea5537c9 completed May 9, 2026, 11:22 p.m.
Created at: May 3, 2026, 4:21 p.m.