Triple
T7974640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drohobych |
E185412
|
entity |
| Predicate | twinTown |
P1072
|
FINISHED |
| Object | Tarnów |
E23368
|
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: Tarnów | Statement: [Drohobych, twinTown, Tarnów]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tarnów Context triple: [Drohobych, twinTown, Tarnów]
-
A.
Tarnów
chosen
Tarnów is a historic city in southern Poland known for its well-preserved Old Town, Renaissance architecture, and cultural heritage.
-
B.
Przemyśl
Przemyśl is a historic city in southeastern Poland near the Ukrainian border, known for its strategic location, multicultural heritage, and well-preserved fortifications.
-
C.
Kielce
Kielce is a city in south-central Poland known as an important regional center for industry, education, and culture.
-
D.
Kalisz
Kalisz is one of Poland’s oldest cities, located in the Greater Poland region and known for its historical architecture and cultural heritage.
-
E.
Hrubieszów
Hrubieszów is a historic town in eastern Poland near the Ukrainian border, known for its multicultural heritage and location in the Lublin region.
- 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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bf42a508190bb661fce34ec0151 |
completed | March 31, 2026, 3:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e462472ed88190a76b04157c235c80 |
completed | April 19, 2026, 5:04 a.m. |
Created at: March 30, 2026, 5:14 p.m.