Triple

T13230868
Position Surface form Disambiguated ID Type / Status
Subject Bolesławiec E315012 entity
Predicate hasNearbyCity P350 FINISHED
Object Jelenia Góra 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: Jelenia Góra | Statement: [Bolesławiec, hasNearbyCity, Jelenia Góra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jelenia Góra
Context triple: [Bolesławiec, hasNearbyCity, Jelenia Góra]
  • A. Jelenia Góra chosen
    Jelenia Góra is a historic city in southwestern Poland, known for its picturesque setting in the Karkonosze Mountains and its well-preserved old town architecture.
  • B. Zielona Góra
    Zielona Góra is a city in western Poland known for its wine-making tradition and annual wine festival.
  • C. Gorzów Śląski
    Gorzów Śląski is a small town in southwestern Poland known for its location in the historical region of Upper Silesia.
  • D. Glogów
    Glogów is a historic town in western Poland on the Oder River, known for its medieval origins and reconstructed Old Town.
  • E. Polkowice
    Polkowice is a town in southwestern Poland known for its copper mining industry and location within the Lower Silesian region.
  • 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_69d806affc688190a25b6ccc588e9c72 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98d336ae08190bfc118cfbefddf84 completed April 10, 2026, 11:52 p.m.
Created at: April 9, 2026, 9:22 p.m.