Triple
T11210178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porąbka |
E265283
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Siewierz |
E925336
|
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: Siewierz | Statement: [Porąbka, locatedNear, Siewierz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Siewierz Context triple: [Porąbka, locatedNear, Siewierz]
-
A.
Siewierz
chosen
Siewierz is a historic town in southern Poland, known for its medieval castle ruins and location within the Silesian region.
-
B.
Świerklaniec
Świerklaniec is a village and municipality in southern Poland’s Silesian Voivodeship, known for its historic park complex and inclusion in the industrial-urban region around Katowice.
-
C.
Strzyżów
Strzyżów is a small town in southeastern Poland, located in the Subcarpathian region and known for its picturesque setting among the Carpathian foothills.
-
D.
Sianów
Sianów is a small town in northwestern Poland known for its historical ties to the Pomerania region and its location near the Baltic coast.
-
E.
Brzesko
Brzesko is a town in southern Poland known for its historical architecture and regional brewing traditions.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d6f5d4819086dcb776a0d469e8 |
completed | April 9, 2026, 5:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fee5da6a2081909dcc9785598e1196 |
completed | May 9, 2026, 7:44 a.m. |
Created at: April 8, 2026, 9:30 p.m.