Triple

T28970907
Position Surface form Disambiguated ID Type / Status
Subject Horodok, Khmelnytskyi Oblast E734268 entity
Predicate historicalJewishPopulation P91263 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: [Horodok, Khmelnytskyi Oblast, historicalJewishPopulation, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalJewishPopulation
Context triple: [Horodok, Khmelnytskyi Oblast, historicalJewishPopulation, yes]
  • A. hadSignificantJewishPopulationBeforeWorldWarII
    Indicates that the subject place or region had a notably large or influential Jewish community prior to the outbreak of World War II.
  • B. hasJewishCommunityHistory chosen
    Indicates that there is a documented history of a Jewish community being present, active, or influential in relation to the subject.
  • C. historicalPopulationContext
    Indicates the relationship between a population figure and the specific historical period or circumstances in which that population size occurred.
  • D. hasSignificantJewishCommunity
    Indicates that a place or entity possesses a notably large, influential, or historically important Jewish community.
  • E. historicalPopulationMovement
    Indicates the movement or migration of a population from one place to another during a specific historical period or event.
  • 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_69f05b0d1e7c819092baab93d3fe277e completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69fe629b4fa481908467c7c41b77f0c6 completed May 8, 2026, 10:24 p.m.
PD Predicate disambiguation batch_69fe61bb260c819083f9378a3a06ca47 completed May 8, 2026, 10:20 p.m.
Created at: April 28, 2026, 9:05 a.m.