Triple
T11112881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Borderlands |
E262804
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Pińsk |
E480423
|
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: Pińsk | Statement: [Eastern Borderlands, hasMajorCity, Pińsk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pińsk Context triple: [Eastern Borderlands, hasMajorCity, Pińsk]
-
A.
Pińsk
chosen
Pińsk is a historic city in present-day Belarus, known as a cultural and religious center of the Polesia region and formerly part of the eastern borderlands of Poland (Kresy).
-
B.
Pieńsk
Pieńsk is a small town in southwestern Poland near the German border, known for its location along the Lusatian Neisse River in the Lower Silesian region.
-
C.
Pruzhany
Pruzhany is a historic town in western Belarus known for its cultural heritage and role as a local administrative and economic center.
-
D.
Pałuki
Pałuki is a historical and ethnographic region in north-central Poland, known for its distinctive folk culture, wooden architecture, and numerous lakes.
-
E.
Radzyń Podlaski
Radzyń Podlaski is a historic town in eastern Poland known for its Baroque Potocki Palace and role as a local cultural and administrative 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79aa523588190a25d241ccc6a9679 |
completed | April 9, 2026, 12:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e42d78c71c81908671a93ac5196c0a |
completed | April 19, 2026, 1:18 a.m. |
Created at: April 8, 2026, 9:27 p.m.