Triple

T10473270
Position Surface form Disambiguated ID Type / Status
Subject Wieluń E246981 entity
Predicate hasTwinTown P919 FINISHED
Object Stryi E661981 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: Stryi | Statement: [Wieluń, hasTwinTown, Stryi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stryi
Context triple: [Wieluń, hasTwinTown, Stryi]
  • A. Stryi chosen
    Stryi is a historic city in western Ukraine known as an important regional center of the Lviv Oblast.
  • B. Kryvorivnia
    Kryvorivnia is a traditional Hutsul mountain village in western Ukraine known for its rich folk culture and picturesque Carpathian landscapes.
  • C. Rubizhne
    Rubizhne is an industrial city in eastern Ukraine known for its chemical and manufacturing industries and its location within the conflict-affected Donbas region.
  • D. Pervomaiskyi
    Pervomaiskyi is a small industrial city in eastern Ukraine known for its chemical industry and location within Kharkiv Oblast.
  • E. Verkhovyna
    Verkhovyna is a mountainous village and popular tourist destination in the Carpathian region of western Ukraine, known for its Hutsul culture and scenic landscapes.
  • 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_69d381c16c248190a2fe5b471e584e9c completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d5094daac081908e0ba5e10c1bbb67 completed April 7, 2026, 1:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69d90db8b1288190bb6bb064cb0724e0 completed April 10, 2026, 2:48 p.m.
Created at: April 6, 2026, 12:20 p.m.