Triple
T6704173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oświęcim County |
E152956
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | City of Jaworzno |
E251901
|
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: City of Jaworzno | Statement: [Oświęcim County, borders, City of Jaworzno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: City of Jaworzno Context triple: [Oświęcim County, borders, City of Jaworzno]
-
A.
Jaworzno
chosen
Jaworzno is a city in southern Poland, located in the Silesian Voivodeship and known for its industrial heritage and role in the Upper Silesian urban area.
-
B.
Jedwabno
Jedwabno is a small town in northern Poland located within the Warmian-Masurian Voivodeship, an area known for its lakes and forests.
-
C.
Chorzów
Chorzów is an industrial city in southern Poland’s Silesian region, known for its heavy industry heritage and the extensive Silesian Park.
-
D.
Kociewie
Kociewie is an ethnocultural region in northern Poland known for its distinct folk traditions, dialect, and rural landscapes.
-
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 (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_69c68807adbc8190b8632df42b39eda0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d0e919748190953d893eb61724e7 |
completed | March 27, 2026, 6:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c70085ed8c81909cb407ab183ebbe5 |
completed | March 27, 2026, 10:11 p.m. |
Created at: March 27, 2026, 2:06 p.m.