Triple

T17831544
Position Surface form Disambiguated ID Type / Status
Subject Telšiai E445267 entity
Predicate hasTwinTown P919 FINISHED
Object Võru 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: Võru | Statement: [Telšiai, hasTwinTown, Võru]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Võru
Context triple: [Telšiai, hasTwinTown, Võru]
  • A. Võru chosen
    Võru is a small town in southeastern Estonia known for its lakeside setting, traditional Võro culture, and role as a regional administrative and cultural center.
  • B. Jõhvi
    Jõhvi is a town in northeastern Estonia that serves as the administrative center of Ida-Viru County.
  • C. Põlva
    Põlva is a small town in southeastern Estonia known as a local administrative and cultural center surrounded by lakes and forested landscapes.
  • D. Haapsalu
    Haapsalu is a small seaside town in western Estonia known for its historic wooden architecture, medieval castle, and traditional seaside resort and spa culture.
  • E. Kohtla-Järve
    Kohtla-Järve is an industrial city in northeastern Estonia known for its oil shale industry and diverse population.
  • 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_69d8b9f1a6d881909f024bc603111cdb completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48d248ecc8190b3f0d001b539d960 completed April 19, 2026, 8:07 a.m.
Created at: April 10, 2026, 10:15 a.m.