Triple
T7974633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drohobych |
E185412
|
entity |
| Predicate | twinTown |
P1072
|
FINISHED |
| Object | Bolesławiec |
E315012
|
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: Bolesławiec | Statement: [Drohobych, twinTown, Bolesławiec]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bolesławiec Context triple: [Drohobych, twinTown, Bolesławiec]
-
A.
Bolesławiec
chosen
Bolesławiec is a historic town in southwestern Poland renowned for its traditional hand-decorated pottery.
-
B.
Zbrzyca
Zbrzyca is a river in northern Poland that flows through the Pomeranian region before joining the Brda River.
-
C.
Brzesko
Brzesko is a town in southern Poland known for its historical architecture and regional brewing traditions.
-
D.
Glogów
Glogów is a historic town in western Poland on the Oder River, known for its medieval origins and reconstructed Old Town.
-
E.
Racibórz
Racibórz is a historic town in southern Poland, located in the Silesian region near the Czech border, known for its medieval heritage and industrial traditions.
- 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_69f4578899ac81908b6e3c8948ca6628 |
completed | May 1, 2026, 7:34 a.m. |
Created at: March 30, 2026, 5:14 p.m.