Triple
T15856390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lubawa |
E384466
|
entity |
| Predicate | nearbyCity |
P350
|
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: [Lubawa, nearbyCity, Iława]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Iława Context triple: [Lubawa, nearbyCity, 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.
Iłowa
Iłowa is a small town in western Poland located in the Lubusz Voivodeship.
-
C.
Iłża
Iłża is a historic town in east-central Poland known for the ruins of its medieval castle and its location near the city of Radom.
-
D.
Oława
Oława is a historic town in southwestern Poland, located in Lower Silesia near Wrocław.
-
E.
Słupia
Słupia is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e14cb08bd081908af2120eb2925441 |
completed | April 16, 2026, 8:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa14c1e508190a182db216cc4e326 |
completed | May 9, 2026, 9:04 p.m. |
Created at: April 10, 2026, 4:50 a.m.