Triple

T2057160
Position Surface form Disambiguated ID Type / Status
Subject Włodawa E45699 entity
Predicate minorityLanguageTradition P6149 FINISHED
Object Yiddish 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: Yiddish | Statement: [Włodawa, minorityLanguageTradition, Yiddish]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: minorityLanguageTradition
Context triple: [Włodawa, minorityLanguageTradition, Yiddish]
  • A. heritageLanguage chosen
    Indicates that one entity is the ancestral or culturally inherited language associated with another entity.
  • B. minorityLanguagePolicy
    Indicates a policy or set of rules governing the recognition, protection, and use of languages spoken by minority groups within a larger political or social context.
  • C. culturalTradition
    Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
  • D. traditionalLanguageName
    Indicates the name traditionally used in a particular language to refer to the subject entity.
  • E. isCulturalLanguageOf
    Indicates that a language serves as a primary medium of cultural expression, identity, and heritage for a particular group, community, or region.
  • 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_69a8891a19508190a12ef1e192308dcb completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abb9abdb088190991a620e01dc226f completed March 7, 2026, 5:37 a.m.
PD Predicate disambiguation batch_69abb7ad5a7c8190b92575d6053b3fb7 completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:40 p.m.