Triple
T11161070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warmian-Masurian Voivodeship |
E264035
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Iława |
E222330
|
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: Iława | Statement: [Warmian-Masurian Voivodeship, containsCity, Iława]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Iława Context triple: [Warmian-Masurian Voivodeship, containsCity, Iława]
-
A.
Iława
chosen
Iława is a town in northern Poland known for its lakeside location on Jeziorak Lake and its role as a local economic and tourist center in the Warmian-Masurian region.
-
B.
Oława
Oława is a historic town in southwestern Poland, located in Lower Silesia near Wrocław.
-
C.
Słupia
Słupia is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
-
D.
Motława
Motława is a river in northern Poland that flows through the historic city of Gdańsk and into the Vistula Lagoon.
-
E.
Skawina
Skawina is a town in southern Poland near Kraków, known for its industrial facilities and role as a local economic and transport hub.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8817a90819087820d5241c58851 |
completed | April 9, 2026, 5:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4636268d0819088873f2062115506 |
completed | April 19, 2026, 5:08 a.m. |
Created at: April 8, 2026, 9:29 p.m.