Triple

T22146189
Position Surface form Disambiguated ID Type / Status
Subject Stalowa Wola County E547293 entity
Predicate borderedBy P224 FINISHED
Object Janów Lubelski County 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: Janów Lubelski County | Statement: [Stalowa Wola County, borderedBy, Janów Lubelski County]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Janów Lubelski County
Context triple: [Stalowa Wola County, borderedBy, Janów Lubelski County]
  • A. Janów Lubelski chosen
    Janów Lubelski is a small town in eastern Poland known for its surrounding forests, lakes, and role as a local administrative and tourist center.
  • B. Janowo
    Janowo is a town in northern Poland located in the Warmian-Masurian Voivodeship, a region known for its lakes and forests.
  • C. Chojnów
    Chojnów is a historic town in southwestern Poland, known for its medieval origins and long association with the Silesian Piast dynasty.
  • D. Janowiec Wielkopolski
    Janowiec Wielkopolski is a small town in north-central Poland, situated in the historic Pałuki region of the Kuyavian-Pomeranian Voivodeship.
  • E. Janinów
    Janinów is a village located within the administrative district of Gmina Bielawy in central Poland.
  • 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_69e11e3a95d88190a3bd80d9471976c3 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f129f097248190a8a3cdff1593b5b5 completed April 28, 2026, 9:43 p.m.
Created at: April 16, 2026, 8:33 p.m.