Triple
T2845124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichsgau Wartheland |
E62564
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Kalisz |
E133882
|
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: Kalisz | Statement: [Reichsgau Wartheland, containsCity, Kalisz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kalisz Context triple: [Reichsgau Wartheland, containsCity, 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.
Kielce
Kielce is a city in south-central Poland known as an important regional center for industry, education, and culture.
-
C.
Bielsko-Biała
Bielsko-Biała is a city in southern Poland at the foot of the Beskid Mountains, known as a regional industrial and cultural center formed from the historic towns of Bielsko and Biała.
-
D.
Tarnów
Tarnów is a historic city in southern Poland known for its well-preserved Old Town, Renaissance architecture, and cultural heritage.
-
E.
Suwałki
Suwałki is a city in northeastern Poland known for its cold climate, proximity to the Lithuanian border, and location within the historical region of Podlasie.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf1b58c88190b45d8c5a76dc52ac |
completed | March 7, 2026, 8:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be89b0441881908b87c7a62434e79a |
completed | March 21, 2026, 12:06 p.m. |
Created at: March 6, 2026, 10:02 p.m.