Triple
T9189863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orneta |
E220553
|
entity |
| Predicate | neighboringTown |
P3883
|
FINISHED |
| Object | Pieniężno |
E220552
|
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: Pieniężno | Statement: [Orneta, neighboringTown, Pieniężno]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pieniężno Context triple: [Orneta, neighboringTown, Pieniężno]
-
A.
Pieniężno
chosen
Pieniężno is a small town in northern Poland known for its historic architecture and location within the picturesque Warmian-Masurian region.
-
B.
Szerzyny
Szerzyny is a village in southern Poland located within the administrative region of Lesser Poland Voivodeship.
-
C.
Pyrzyce
Pyrzyce is a historic town in northwestern Poland known for its medieval fortifications and location within the West Pomeranian region.
-
D.
Zawichost
Zawichost is a small historic town in southeastern Poland, situated on the Vistula River in the Świętokrzyskie Voivodeship.
-
E.
Piastów
Piastów is a small town in east-central Poland that functions as a residential suburb within the Warsaw metropolitan area.
- 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_69ccd5bd8c5c81909d0cdbcd7410fcee |
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.