Triple

T17927498
Position Surface form Disambiguated ID Type / Status
Subject Tarnopol Voivodeship E448234 entity
Predicate containsCity P294 FINISHED
Object Husiatyn 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: Husiatyn | Statement: [Tarnopol Voivodeship, containsCity, Husiatyn]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Husiatyn
Context triple: [Tarnopol Voivodeship, containsCity, Husiatyn]
  • A. Husiatyn chosen
    Husiatyn is a small historic town in western Ukraine known for its multicultural heritage and architectural landmarks, including old synagogues and churches.
  • B. Horki
    Horki is a town in eastern Belarus known for its agricultural academy and regional administrative significance.
  • C. Huchnom
    Huchnom refers to a subgroup of the Yuki people, an Indigenous group native to what is now Northern California.
  • D. Huta
    Huta is a village located in western Ukraine’s Ivano-Frankivsk Oblast, known for its proximity to the Carpathian Mountains and forested landscapes.
  • E. Harsusi
    Harsusi is a critically endangered South Semitic language spoken by a small community in the Dhofar region of Oman.
  • 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_69d8b9f79d14819095540856928f0e25 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4a54f29a88190b035d8473765bde5 completed April 19, 2026, 9:50 a.m.
Created at: April 10, 2026, 10:20 a.m.