Triple

T17425868
Position Surface form Disambiguated ID Type / Status
Subject Holocaust in Eastern Galicia E423735 entity
Predicate location P40 FINISHED
Object Tarnopol NE NERFINISHED

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: Tarnopol | Statement: [Holocaust in Eastern Galicia, location, Tarnopol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tarnopol
Context triple: [Holocaust in Eastern Galicia, location, Tarnopol]
  • A. Tarnopol chosen
    Tarnopol is a historic city in western Ukraine, now known as Ternopil, which has long served as a regional cultural and administrative center.
  • B. Radomyshl
    Radomyshl is a historic town in northern Ukraine, known for its Jewish heritage and role within the Zhytomyr Oblast region.
  • C. Kraśnik
    Kraśnik is a town in eastern Poland known for its historical architecture and location within the Lublin region.
  • D. Horodok
    Horodok is a small town in western Ukraine known for its historical roots and location within the Khmelnytskyi region.
  • E. Stanisławów
    Stanisławów is a historic city in the former eastern borderlands of Poland (now Ivano-Frankivsk in Ukraine), known for its multicultural heritage and shifting political history.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889d88b6081908bada047f5b3ba51 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e448fbfda88190be1c001d64289bf7 completed April 19, 2026, 3:16 a.m.
Created at: April 10, 2026, 5:46 a.m.