Triple
T9190315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gronowo Elbląskie |
E220567
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | city of Elbląg |
E330705
|
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: city of Elbląg | Statement: [Gronowo Elbląskie, locatedNear, city of Elbląg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: city of Elbląg Context triple: [Gronowo Elbląskie, locatedNear, city of Elbląg]
-
A.
Bydgoszcz
Bydgoszcz is a major city in northern Poland known as an important economic, cultural, and academic center on the Brda and Vistula rivers.
-
B.
Lublin
Lublin is a historic city in eastern Poland known as a major cultural, academic, and economic center and for its significant role in Polish political history.
-
C.
Elbląg
chosen
Elbląg is a historic city in northern Poland known for its reconstructed Old Town, medieval heritage, and role as an important port and industrial center.
-
D.
Zamość
Zamość is a Renaissance-planned city in southeastern Poland, renowned for its well-preserved Old Town and UNESCO World Heritage status.
-
E.
Ostróda
Ostróda is a town in northern Poland known for its lakeside setting, tourism, and role as a local economic and cultural center.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd5bf25c081909e651b67ef8ecc33 |
completed | April 1, 2026, 8:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d05c272f508190aade1769c88cf16d |
completed | April 4, 2026, 12:32 a.m. |
Created at: March 30, 2026, 7:24 p.m.