Triple
T1474341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shrewsbury |
E30803
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Glogów |
E18473
|
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: Glogów | Statement: [Shrewsbury, hasTwinTown, Glogów]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Glogów Context triple: [Shrewsbury, hasTwinTown, Glogów]
-
A.
Glogów
chosen
Glogów is a historic town in western Poland on the Oder River, known for its medieval origins and reconstructed Old Town.
-
B.
Ojców
Ojców is a small village in southern Poland known as a gateway to the picturesque Ojców National Park in the Kraków-Częstochowa Upland.
-
C.
Bolesławiec
Bolesławiec is a historic town in southwestern Poland renowned for its traditional hand-decorated pottery.
-
D.
Polkowice
Polkowice is a town in southwestern Poland known for its copper mining industry and location within the Lower Silesian region.
-
E.
Kociewie
Kociewie is an ethnocultural region in northern Poland known for its distinct folk traditions, dialect, and rural landscapes.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c6011d248190988380eca4ecf514 |
completed | March 1, 2026, 11:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b235106b1c8190ae6d4d02aefd69a9 |
completed | March 12, 2026, 3:37 a.m. |
Created at: March 1, 2026, 8:11 p.m.