Triple

T12656493
Position Surface form Disambiguated ID Type / Status
Subject Międzyrzec Podlaski E302296 entity
Predicate historicalMinorityLanguage P106031 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: [Międzyrzec Podlaski, historicalMinorityLanguage, Yiddish]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalMinorityLanguage
Context triple: [Międzyrzec Podlaski, historicalMinorityLanguage, Yiddish]
  • A. historicalMinority
    Indicates that an entity has been part of a group that has been numerically, politically, or socially subordinate within a society over a significant historical period.
  • B. hasMajorityLanguageHistorically
    Indicates that a particular language has historically been the predominant or majority language within a given entity or region.
  • C. historicalLanguageGroup
    Indicates that two or more entities belong to the same historically defined language group or family, based on shared linguistic ancestry or development.
  • D. heritageLanguage
    Indicates that one entity is the ancestral or culturally inherited language associated with another entity.
  • E. historicalLanguage
    Indicates that one language is a historical or earlier form/ancestor of another language.
  • F. None of above. chosen

Provenance (4 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_69d7bded71a88190bb76e2413af9ea66 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9617b07ec8190b714f04ae6654060 completed April 10, 2026, 8:45 p.m.
PD Predicate disambiguation batch_69d960b78ce8819091f15dd5013e6da5 completed April 10, 2026, 8:42 p.m.
PDg Predicate description generation batch_69d96179c7648190a05a13991d62bebb completed April 10, 2026, 8:45 p.m.
Created at: April 9, 2026, 5:18 p.m.