Triple
T2830870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lublin Voivodeship |
E62231
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Zamość |
E61054
|
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: Zamość | Statement: [Lublin Voivodeship, contains, Zamość]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zamość Context triple: [Lublin Voivodeship, contains, Zamość]
-
A.
Zamość
chosen
Zamość is a Renaissance-planned city in southeastern Poland, renowned for its well-preserved Old Town and UNESCO World Heritage status.
-
B.
Wadowice
Wadowice is a historic town in southern Poland best known as the birthplace of Pope John Paul II.
-
C.
Tarnów
Tarnów is a historic city in southern Poland known for its well-preserved Old Town, Renaissance architecture, and cultural heritage.
-
D.
Augustów
Augustów is a town in northeastern Poland known for its lakes, forests, and popular water tourism, including the historic Augustów Canal.
-
E.
Lubawa
Lubawa is a historic town in northern Poland known for its medieval heritage and location within the Warmian-Masurian 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_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_69bdc4fea8fc8190bf99d53fc56d7d39 |
completed | March 20, 2026, 10:06 p.m. |
Created at: March 6, 2026, 10:01 p.m.