Triple
T2830878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lublin Voivodeship |
E62231
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Włodawa |
E45699
|
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: Włodawa | Statement: [Lublin Voivodeship, contains, Włodawa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Włodawa Context triple: [Lublin Voivodeship, contains, Włodawa]
-
A.
Włodawa
chosen
Włodawa is a town in eastern Poland near the borders with Belarus and Ukraine, known for its multicultural heritage and proximity to the former Sobibor extermination camp.
-
B.
Biała Podlaska
Biała Podlaska is a city in eastern Poland near the Belarusian border, known as a local economic and cultural center of the Lublin Voivodeship.
-
C.
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.
-
D.
Biłgoraj
Biłgoraj is a town in eastern Poland known for its traditional wooden architecture and location near the Roztocze region.
-
E.
Tarnobrzeg
Tarnobrzeg is a city in southeastern Poland known historically for its sulfur mining industry and location along the Vistula River.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdebd5a2c81908f0e30a0ae0eb8df |
completed | March 7, 2026, 8:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be393b31e081908b585a88a35d4c39 |
completed | March 21, 2026, 6:22 a.m. |
Created at: March 6, 2026, 10:01 p.m.