Triple
T22748517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town Hall of Kalisz |
E562622
|
entity |
| Predicate | ownedBy |
P347
|
FINISHED |
| Object | City of Kalisz |
—
|
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: City of Kalisz | Statement: [Town Hall of Kalisz, ownedBy, City of Kalisz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: City of Kalisz Context triple: [Town Hall of Kalisz, ownedBy, City of Kalisz]
-
A.
Kalisz
chosen
Kalisz is one of Poland’s oldest cities, located in the Greater Poland region and known for its historical architecture and cultural heritage.
-
B.
Zamość
Zamość is a Renaissance-planned city in southeastern Poland, renowned for its well-preserved Old Town and UNESCO World Heritage status.
-
C.
Kamieniec Ząbkowicki
Kamieniec Ząbkowicki is a village in southwestern Poland known for its historic palace complex and role as a regional railway junction.
-
D.
Lubin
Lubin is a town in southwestern Poland known for its copper mining industry and location within the Lower Silesian region.
-
E.
Krotoszyn
Krotoszyn is a historic town in west-central Poland known for its medieval origins and changing political affiliations, including periods under Prussian and German rule.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179b702388190b134dde5f80ea3cd |
completed | April 29, 2026, 3:23 a.m. |
Created at: April 17, 2026, 3:24 p.m.