Triple

T13230866
Position Surface form Disambiguated ID Type / Status
Subject Bolesławiec E315012 entity
Predicate hasNearbyCity P350 FINISHED
Object Zgorzelec E222843 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: Zgorzelec | Statement: [Bolesławiec, hasNearbyCity, Zgorzelec]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zgorzelec
Context triple: [Bolesławiec, hasNearbyCity, Zgorzelec]
  • A. Zgorzelec chosen
    Zgorzelec is a town in southwestern Poland on the Lusatian Neisse River, forming a twin city with Görlitz in Germany and serving as an important local cultural and transport hub.
  • B. Samborzec
    Samborzec is a village and the seat of a rural administrative district in southeastern Poland’s Sandomierz County.
  • C. Chełmek
    Chełmek is a small town in southern Poland known historically for its shoe industry and its location near Oświęcim (Auschwitz).
  • D. Zbrzyca
    Zbrzyca is a river in northern Poland that flows through the Pomeranian region before joining the Brda River.
  • E. Huczwa
    Huczwa is a river in eastern Poland that flows through the Lublin region before joining the Western Bug.
  • 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_69d806affc688190a25b6ccc588e9c72 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98d336ae08190bfc118cfbefddf84 completed April 10, 2026, 11:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6ff2c07488190ad07c544cca63a7d completed May 3, 2026, 7:54 a.m.
Created at: April 9, 2026, 9:22 p.m.