Triple

T9257543
Position Surface form Disambiguated ID Type / Status
Subject Mike Mazurki E222483 entity
Predicate placeOfBirth P1 FINISHED
Object Tarnopol E613690 NE 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: Tarnopol | Statement: [Mike Mazurki, placeOfBirth, Tarnopol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tarnopol
Context triple: [Mike Mazurki, placeOfBirth, 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. 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.
  • E. Lwów
    Lwów is a historic city in Eastern Europe, now known as Lviv in western Ukraine, long recognized as a major cultural and political center of the region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca841e4cd481908e738c74e958eaea completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd06b660448190b6bc04beff0f5512 completed April 1, 2026, 11:51 a.m.
NED1 Entity disambiguation (via context triple) batch_69d100b8f80c8190bef93de787227a51 completed April 4, 2026, 12:14 p.m.
Created at: March 30, 2026, 7:32 p.m.