Triple
T5954545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defense of Zamość (1920) |
E132478
|
entity |
| Predicate | hasLocation |
P40
|
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: [Defense of Zamość (1920), hasLocation, Zamość]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zamość Context triple: [Defense of Zamość (1920), hasLocation, 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.
Zduńska Wola
Zduńska Wola is a town in central Poland known historically as a textile and industrial center.
-
D.
Tarnów
Tarnów is a historic city in southern Poland known for its well-preserved Old Town, Renaissance architecture, and cultural heritage.
-
E.
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.
- 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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c039c054a48190ace32250c43e29b4 |
completed | March 22, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c99ba1bbdc81909269ac0a97caa91d |
completed | March 29, 2026, 9:37 p.m. |
Created at: March 22, 2026, 4:02 p.m.