Triple

T18196863
Position Surface form Disambiguated ID Type / Status
Subject Tychy E435682 entity
Predicate locatedNear P294 FINISHED
Object Bieruń 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: Bieruń | Statement: [Tychy, locatedNear, Bieruń]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bieruń
Context triple: [Tychy, locatedNear, Bieruń]
  • A. Bieruń chosen
    Bieruń is a small town in southern Poland known for its historic architecture, coal-mining heritage, and location within the Silesian Voivodeship.
  • B. Byczyna
    Byczyna is a historic small town in southwestern Poland known for its well-preserved medieval urban layout and defensive walls.
  • C. Borów
    Borów is a small settlement located within the administrative district of Gmina Bukowno in southern Poland.
  • D. Siewierz
    Siewierz is a historic town in southern Poland, known for its medieval castle ruins and location within the Silesian region.
  • E. Gubałówka
    Gubałówka is a popular hill and tourist destination in the Polish Tatra region, known for its panoramic views of Zakopane and the surrounding mountains.
  • 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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e0d377d48190869a033d12f6ee80 completed April 19, 2026, 2:04 p.m.
Created at: April 10, 2026, 10:31 a.m.