Triple

T4136805
Position Surface form Disambiguated ID Type / Status
Subject Shche ne vmerla Ukraina E85173 entity
Predicate hasOfficialLyricsVersion P29645 FINISHED
Object 2003 revision 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: 2003 revision | Statement: [Shche ne vmerla Ukraina, hasOfficialLyricsVersion, 2003 revision]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOfficialLyricsVersion
Context triple: [Shche ne vmerla Ukraina, hasOfficialLyricsVersion, 2003 revision]
  • A. hasOfficialLyrics chosen
    Indicates that an entity (such as a song or musical work) has lyrics that are formally recognized or authorized as the official version.
  • B. hasUnofficialLyrics
    Indicates that an entity is associated with lyrics that are not officially authorized or recognized by the original creator or rights holder.
  • C. hasLyric
    Indicates that one entity (typically a musical work or track) contains or is associated with the lyrics provided by another entity.
  • D. hasExplicitLyrics
    Indicates that the referenced content contains explicit language or themes, such as profanity, sexual content, or strong violence.
  • E. hasLyricsSource
    Indicates that one entity serves as the source or origin of the lyrics associated with 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_69aed935ccd881909dc61f81bcdb7a78 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af03a0f3408190adba7a8513bd3d12 completed March 9, 2026, 5:30 p.m.
PD Predicate disambiguation batch_69af018a54848190987f18c066c75068 completed March 9, 2026, 5:21 p.m.
Created at: March 9, 2026, 3:43 p.m.